-
Notifications
You must be signed in to change notification settings - Fork 47
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
Update spack-stack-dev from spack develop as of 2024/10/31 #1363
Update spack-stack-dev from spack develop as of 2024/10/31 #1363
Conversation
….1, and remove noavx512 variant for openblas
…eature/update_from_spack_dev_20241031
…ci-x86_64-intel.yaml
…eature/update_from_spack_dev_20241031
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 looks good to me. Thanks for all the work to get our spack fork sync'd up!
This looks really good. The only issue I encountered in testing is that I'll need to pin the GDAL version in the NCO template. Is it alright if I add this here, or would you prefer it in a followup PR? |
Thanks for testing! Feel free to push to this PR. |
@AlexanderRichert-NOAA I'll merge the spack PR for the update from spack dev and update the submodule pointer here, but will wait for your gdal nco update before merging this. |
Done, thanks |
Summary
-a
flag fromspack buildcache push
for all GitHub actions workflows+classic-names
to theintel-oneapi-mpi
external package definition in GitHub actions. May need to do the same for each of the preconfigured sites when usingicc
+icpc
+ifort
. Without+classic-names
, it works foricx
+icpx
+ifort
and for ``icx+
icpx`+`ifx`.configs/common/packages.yaml
to remove deprecated variants and pin certain packages to avoid duplicate packagesesmf
, for some reason the concretizer didn't realize this until nowTesting
Describe the testing done for this PR.
[email protected]
, compiled NEPTUNE with it[email protected]
, compiled NEPTUNE with it[email protected]
Applications affected
Potentially all
Systems affected
None directly
Dependencies
Issue(s) addressed
Resolves #1181
Checklist