Merge release/1.8.0 into develop #1321
Merged
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
Co-authored-by: role-r2d2-admin <[email protected]>
During testing of an early 1.8.0 candidate, it was found that compiling numpy v1.25.x and matplotlib v3.8.x together with Intel caused matplotlib to fail to generate basic plots that included tick marks. Reverting the versions to 1.23.5 and 3.7.4 resolved the issue. This version does not work on Acorn with Intel 19, but other than for newer versions of Intel, numpy-1.24.4 works there. Therefore, there will be a follow-up PR that changes the default py-numpy version on Acorn for Intel 19 only to 1.24.4.
…move release-specific site documentation for preconfigured sites to Wiki (JCSDA#1280) 1. Site config updates: - Add AOCC config for Nautilus, update oneAPI config; for AOCC, add configs/common/packages_aocc.yaml (identical to packages_gcc.yaml; both use intel-oneapi-mkl from the new oneAPI compilers 2024.2.1) - Update oneAPI config for Blackpearl - Move Casper site config from tier1 to tier2 (long agreed upon and already in the documentation) 2. In neptune-env virtual package, use sp with AOCC and ip with all other compilers (so that we can build the NEPTUNE standalone environment with AOCC) 3. Documentation updates: move release-specific site documentation to Wiki - see https://github.com/JCSDA/spack-stack/wiki , https://github.com/JCSDA/spack-stack/wiki/spack%E2%80%90stack%E2%80%901.8.0-release-documentation , and https://spack-stack--1280.org.readthedocs.build/en/1280/
…pack package, remove from container configs (JCSDA#1287) For release/1.8.0: Update submodule pointer for spack for the changes in JCSDA/spack#477. Remove g2 compiler flags in container configs, since these are now in the g2 package itself. Also include a bug fix to adjust the py-numpy version to match what is in configs/common/packages.yaml since yesterday (1.23.5).
This PR adds in configuration to enable building on the latest versions of the MacOS and Command Line Tools (14.6.1 and 15.3 respectively). The NewSiteConfig.rst documentation has been updated for building on the Mac. --------- Co-authored-by: Dom Heinzeller <[email protected]>
This PR provides updates for the Acorn site config for the 1.8.0 release, which should eventually get merged into develop.
…#1294) This PR borrows the logic from JCSDA#1213 that allows a compiler version to be specified in spack stack create env. It's a couple of tweaks to stack_env.py. This isn't strictly urgent, but I'm hoping to put this in the 1.8.0 release in anticipation of supporting installations by NCO (plus maybe others will find it useful; I know it will be useful for Acorn, and maybe also for NRL?).
More NCO-related updates
JCSDA#1298) Next and hopefully last round of NRL site config and doc updates for release/1.8.0
* Update doc/source/PreConfiguredSites.rst with environment naming conventions table
Update Acorn doco for 1.8.0
* update mkl discover-scu17 package * doc updates for discover
Update Derecho site config for release/1.8.0: 1. Use only three build jobs to avoid getting booted off the system by the arbiter 2. Use [email protected] as backend for Intel to fix build errors for met and py-scipy 3. Pin py-scipy to 1.11.4 4. ecflow/qt changes as discussed earlier
Update changes for NOAA RDHPCS tier1 machines for 1.8.0
71 tasks
climbfuji
requested review from
srherbener,
RatkoVasic-NOAA and
AlexanderRichert-NOAA
RatkoVasic-NOAA
approved these changes
Oct 3, 2024
|
I see some differences with the release/1.8.0 branch, most notably esmf has the '+python' variant in this branch's packages.yaml, and this branch's packages.yaml has a py-ruamel-yaml entry but the 1.8.0 release does not. I don't think there any other differences there that I would potentially care about. |
These are correct and a result of the 1.8.0 release taking such a long time. We merged two PRs into spack-stack develop in the meanwhile that are not part of the release, and this is what you are seeing. |
AlexanderRichert-NOAA
approved these changes
Oct 3, 2024
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.
Summary
All in the title, minus the usual, release-specific changes.
Testing
Applications affected
All
Systems affected
All
Dependencies
Issue(s) addressed
Working towards #1278
Checklist