-
Notifications
You must be signed in to change notification settings - Fork 9
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
Small spack changes to cleanup spack process on HPC Clusters #133
Conversation
buildsystem/spack/load_spack.sh
Outdated
|
||
# Use a directory based environment, and decorate command line | ||
spack env create -d $SPACKENV $base/spack.yaml && |
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.
This is the main change.... No longer are we running spack env create
before a cp
command, we just do it all in one line using spack native commands.
@jaelynlitz please review I think this is good to merge |
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.
Generally looks good, just some small changes requested 😄
9dac54d
to
d67d661
Compare
@jaelynlitz please re-review |
af9879e
to
08da641
Compare
Merge request type
Relates to
This MR updates
Summary
No specific issue being addressed here, just some quality of life changes to some of our spack scripts. This makes it so that the spack environment is created in a single line, and that there is no longer a
module purge
that is ran before config is loaded. This is helpful to prevent harmful environment modifications by our scripts where they might be unnecessary.If these changes are ok, we can extend this to other clusters as needed. Many of the whitespace changes were automatically made by my editor, and we can change / revert as needed. We don't really have any bash linting configuration or developer guidelines surrounding those files...