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
srherbener
left a comment
There was a problem hiding this comment.
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 |
…low-up-mpiifx-mpiifort-site-configs Follow-up to #1363 (update from spack dev 20241031): set correct mpiifx/mpiifort in MPI meta module, update Intel MPI in site configs
Summary
-aflag fromspack buildcache pushfor all GitHub actions workflows+classic-namesto theintel-oneapi-mpiexternal 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+ifortand for ``icx+icpx`+`ifx`.configs/common/packages.yamlto 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.
gcc@13.3.0, compiled NEPTUNE with itoneapi@2024.2.1, compiled NEPTUNE with itgcc@13.3.0Applications affected
Potentially all
Systems affected
None directly
Dependencies
Issue(s) addressed
Resolves #1181
Checklist