-
Notifications
You must be signed in to change notification settings - Fork 714
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
{devel}[foss/2023b] TensorFlow v2.15.1, Bazel v6.3.1, dill v0.3.8, flatbuffers-python v23.5.26, grpcio v1.57.0, ml_dtypes v0.4.0, nsync v1.29.2 #21169
base: develop
Are you sure you want to change the base?
Conversation
…ore-13.2.0.eb, dill-0.3.8-GCCcore-13.2.0.eb, flatbuffers-python-23.5.26-GCCcore-13.2.0.eb, grpcio-1.57.0-GCCcore-13.2.0.eb, ml_dtypes-0.4.0-gfbf-2023b.eb, nsync-1.29.2-GCCcore-13.2.0.eb
@tanmoy1989 A bunch of patch files for Bazel are missing? |
@boegel: thanks, done! |
easybuild/easyconfigs/m/ml_dtypes/ml_dtypes-0.4.0-gfbf-2023b.eb
Outdated
Show resolved
Hide resolved
Co-authored-by: Alexander Grund <Flamefire@users.noreply.github.com>
@@ -69,7 +68,7 @@ exts_list = [ | |||
'checksums': ['aedf21eec7fb2dc91150fc91a1ce12bc44dbb72278a08b58e79ff87c9e28f153'], | |||
}), | |||
('Werkzeug', '3.0.2', { | |||
'source_tmpl': SOURCELOWER_TAR_GZ, | |||
'source_tmpl': '%(namelower)s-%(version)s.tar.gz', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why this change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Honestly the change was not intentional and also not manual. It appeared when I did: "eb --inject-checksums=sha256 --force Tensorflow-2.15.1-foss-2023b.eb
" to include the two new patches - probably due to formatting by EasyBuild/Python?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I opened an issue for that: easybuilders/easybuild-framework#4695
Co-authored-by: Alexander Grund <Flamefire@users.noreply.github.com>
Co-authored-by: Alexander Grund <Flamefire@users.noreply.github.com>
Co-authored-by: Alexander Grund <Flamefire@users.noreply.github.com>
Is there any progress on this PR? I would use dill-0.3.8 in my PR. |
@boegelbot please test @ generoso |
@pavelToman Thanks for triggering the bot. I am not aware of any further progress except me just waiting for someone to review it. |
easybuild/easyconfigs/t/TensorFlow/TensorFlow-2.15.1-foss-2023b.eb
Outdated
Show resolved
Hide resolved
easybuild/easyconfigs/t/TensorFlow/TensorFlow-2.15.1-foss-2023b.eb
Outdated
Show resolved
Hide resolved
…b.eb Co-authored-by: Adam Huffman <verdurin@users.noreply.github.com>
…b.eb Co-authored-by: Adam Huffman <verdurin@users.noreply.github.com>
easybuild/easyconfigs/t/TensorFlow/TensorFlow-2.15.1-foss-2023b.eb
Outdated
Show resolved
Hide resolved
…b.eb Co-authored-by: Adam Huffman <verdurin@users.noreply.github.com>
easybuild/easyconfigs/t/TensorFlow/TensorFlow-2.15.1-foss-2023b.eb
Outdated
Show resolved
Hide resolved
…b.eb Co-authored-by: Adam Huffman <verdurin@users.noreply.github.com>
easybuild/easyconfigs/t/TensorFlow/TensorFlow-2.15.1-foss-2023b.eb
Outdated
Show resolved
Hide resolved
…b.eb Co-authored-by: Adam Huffman <verdurin@users.noreply.github.com>
Test report by @verdurin |
@pavelToman: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... - notification for comment with ID 2456621242 processed Message to humans: this is just bookkeeping information for me, |
@verdurin Looks like the failure is related to |
Test report by @boegelbot |
Yes, I've restarted the build after cleaning up the build node. |
@boegelbot please test @ jsc-zen3 |
@pavelToman: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... - notification for comment with ID 2459478172 processed Message to humans: this is just bookkeeping information for me, |
Test report by @verdurin |
Test report by @boegelbot |
Updated software
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine.
of the built-in python types. Serialization is the process of converting an object to a byte stream, and the inverse | ||
of which is converting a byte stream back to on python object hierarchy.""" | ||
|
||
toolchain = {'name': 'GCCcore', 'version': '13.2.0'} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've opened a separate PR for this exact easyconfig, since it's required by other PRs as a dependency (see #21783 for example):
No action needed in this PR here because of that, just wanted to mention it.
Co-authored-by: Kenneth Hoste <kenneth.hoste@ugent.be>
@boegelbot please test @ jsc-zen3 |
@pavelToman: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... - notification for comment with ID 2464645553 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
@tanmoy1989 I'm not saying we can't merge this, but I'm wondering why you're sticking to TensorFlow v2.15.1 here, and not jumping to a newer release (2.18.0 was released ~3 weeks ago). Did you try, and if so, did you run into particular issues? |
@boegel: I think I tried |
Test report by @boegel |
@boegel Just to add in: I tried
|
@Flamefire What are your thoughts on sticking to TensorFlow 2.15.1 for |
Adding 2.15.1 doesn't mean not adding 2.18.0. We have multiple TF versions in other toolchains too. The trouble with those ML stuff where people require the latest versions of the time. Also in my experience it was always easier to either update the TF version OR the toolchain, not both at the same time. This is what I used to do to avoid having to check too many differences when errors occur. -> Take this and start working on 2.18.0 for 2023b too. |
Yes, I'd be happy to test a |
(created using
eb --new-pr
)2. Bazel-6.3.1_cc-info.patch file (link)