TO BE DISCUSSED AT THE MEETING - Feature/weekly build nrl #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…p of nightly builds Nautilus using GitHub actions
…stack into feature/weekly_build_nautilus
…stack into feature/weekly_build_nautilus
…-env in unified-dev for testing
…il/weekly_build/04_SpackInstall.sh
…eature/weekly_build_nautilus
…into feature/narwhal_oneapi
…l setup currently does not compile Python packages
…into feature/narwhal_oneapi
…eature/narwhal_oneapi
Latest changes in site/packages.yaml and site/modules.yaml config files regarding ecFlow and QT. Removed exclude for creating ecflow modulefile, added path for qt and removed ecflow from package list.
…eature/narwhal_oneapi
* Update site config and documentation for S4 after Rocky8 update (Intel only so far with gcc@13 backend)
…ning ufs-weather-model) (JCSDA#1331) * Update Jet packages_intel.yaml * Update Orion packages_intel.yaml * Update Orion packages_gcc.yaml * Update Hercules packages.yaml
…eature/weekly_build_nautilus
…ve from files in other steps
…in if test for PACKAGES_TO_TEST
This file got merged mistakenly, it doesn't have a `.yaml` suffix and is empty.
…ently unused sites
climbfuji
commented
Oct 22, 2024
util/weekly_build/04_SpackInstall.sh
Outdated
| spack mirror create --dependencies --directory ${mirrorpath?"Source mirror path could not be determined. Check site's mirrors.yaml."} ${PACKAGES_TO_INSTALL:---all} 2>&1 | tee log.fetch | ||
| # Just install the packages we're testing (+dependencies): | ||
| if [[ ! -z "${PACKAGES_TO_TEST}" ]]; then | ||
| spack_install_exe install $INSTALL_OPTS --test root $PACKAGES_TO_TEST | tee log.install-and-test |
There was a problem hiding this comment.
Let's wait with merging until we tested the pipefail stuff
…l/weekly_build/03_SetupEnv.sh
…up.sh, and re-enable .github/workflows/nautilus-nightly-intel.yaml
climbfuji
commented
Oct 23, 2024
|
@AlexanderRichert-NOAA This is ready from my end |
|
@AlexanderRichert-NOAA I successfully built and updated the build-cache with both Intel and oneAPI on Nautilus with this code. |
|
I'll have to wait on testing this until Acorn's available again, mainly I want to check the "spack_wrapper" logic. |
|
Any updates? |
|
@AlexanderRichert-NOAA Updated, please check |
|
This looks good, thanks @climbfuji |
AlexanderRichert-NOAA
merged commit 06faf20
into
AlexanderRichert-NOAA:weekly_build
3 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
WIP
Summary
Describe the changes made in this PR and why they are needed.
Testing
Describe the testing done for this PR.
Applications affected
List all known applications (UFS WM, JEDI, SRW, etc.) intentionally or unintentionally affected by this PR.
Systems affected
List all systems intentionally or unintentionally affected by this PR.
Dependencies
If there are PRs that need to be merged before or along with this one, please add "- [ ] waiting on LINK_TO_PR" for each of them
Issue(s) addressed
Link the issues addressed or resolved by this PR (use
Fixes #???for fully resolved issues)Checklist