-
Notifications
You must be signed in to change notification settings - Fork 48
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
Add weekly build/test scripts #1213
Conversation
closing temporarily so I don't spam the CI with jobs... |
Cron entry for Acorn: |
Co-authored-by: Dom Heinzeller <[email protected]>
…ack into weekly_build
I just noticed that on Acorn, it was creating a directory called "file:" in $SPACK_ENV because of the way it handles the mirror path. I'm tweaking it to drop the "file://" part when it looks up the directory; @rickgrubin-tomorrow @climbfuji please re-test with this change and make sure I didn't break anything... |
Yes, that's fine. I never used |
I just pushed develop into this branch. Once we have approval from EPIC (Rick and or Bruce), we can merge this. |
I need to make one or two last tweaks to the UWM test scripting then it'll be good to go on my end. |
@rickgrubin-noaa I made a few small changes, mainly a couple fixes, plus I'm putting ufs-weather-model under the env directory. This works on Acorn, so if this looks good to you and I didn't break anything for Orion, I'd like to push it as is then later on refine things like having it modify ufs-weather-model modulefiles so we don't need a fork and that sort of thing. Thanks again for adding the UWM testing-- once I added in the shell setup call because of using cron, it ran smoothly. |
All changes are fine with me; nothing breaks on orion. I wasn't testing from cron, thus didn't notice the I had considered modifying Please merge, thank you. |
Summary
This PR will add scripting for weekly unit testing and build caching of the unified env through Jenkins, cron jobs, etc.
Also a few updates for Acorn, including a change to
spack stack create env --compiler
that allows compiler version to be specified (spack stack create env --compiler intel
->envs/myenv-intel
;spack stack create env --compiler intel@2022
->envs/myenv-intel-2022
), which is needed to differentiate onplatformsplatform where more than one version of a compiler is installed.Testing/implementation by platform
On each system:
Platforms (check when all of the above items are complete):
Applications affected
all
Systems affected
all (eventually)
Dependencies
none
Issue(s) addressed
#1184, #365
Checklist