Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Updates to Isambard-3 spack env and purify benchmark #356
Updates to Isambard-3 spack env and purify benchmark #356
Changes from 6 commits
1141060
34dac41
9d704c5
c35480f
7b4aee6
efe8c2d
29bf30e
124bf16
38c1506
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Any reason for using
buildable: false
for this packages? Also, I believe you want also to append^ [email protected]
to all these specs, to avoid making it match with other versions of 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 thought
buildable: false
guarantees that the external will always get used. Is it too strong requirement? Happy to remove it if you think that's better. Adding the python version to the specThere 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.
buildable: false
complicates environment resolution quite a bit whenever a package appears in the environment. I'd expect troubles forpy-numpy
andpy-scipy
because they're somewhat common,py-mpi4py
less so and I'd hope spack links it to the right MPI library anyway.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.
👍 thanks for explaining. My builds seem fine after removing it.
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.
For example, one problem could be the following: for some reason a package in the environment requires a specific version of python and that's not compatible with 3.11.7 (say 3.10 or 3.12), another package needs py-numpy, then you end up in the situation where you can't concretize the environment at all. We do use
buildable: false
for MPI, but we do really want to enforce using system MPI libraries only, I don't see that requirement being useful for python and python packages.