Draft
Conversation
* [skip ci] add oneapi@2025.3.1 compilers and oneapi@2021.17 MPI * [skip ci] add packages_gcc for completeness
…gs for release 2.1 (JCSDA#1947) Update zlib on derecho to v1.2.13. The system-supplied libz libraries are used. Add compiler package configs for gaea-c6. Environments successfully build in personal test location.
Configuration of release/2.1 for building the ue-oneapi-2025.3.0 and ue-gcc-12.4.0 environments on NOAA-AWS Rocky9 cluster.
Site config updates for the current JCSDA maintained ec2 AMIs Note: Because my toolchain changes would also break other site configs in this release, I have removed toolchains from this PR. Testing Locally tested
* Update discover gcc configs * update discover ewok-env to include ecflow
This is a batch of changes to the container environment in 2.1. Additionally this includes an update to the aws-ec2 environment which allows both numpy and aws tools to coexist with the older python setuptools. ### Systems affected CI, containers, ec2. ## Testing Local builds and testing.
* Update .gitmodules: use tags spack-stack-2.1.0 * Update submodule pointer for repos/builtin
…system (JCSDA#1956) Tier1 noaa-azure and noaa-aws: Configuration of release/2.1 for building the ue-oneapi-2025.3.0 and ue-gcc-12.4.0 environments on NOAA-AWS Rocky9 cluster
I did a clean site config build from a fresh clone and found the following issues with aws-ubuntu2404. With these changes the stack builds cleanly in both gcc and oneapi. Issues: JCSDA#1957 - Addressed at the site-config level. TBD if we need this in our common config. JCSDA#1884 - This is built and tested from a clean clone. No further changes for aws-ubuntu2404
…eview and testing
This was referenced Mar 23, 2026
…to feature/merge_rel21_into_develop
climbfuji
force-pushed
the
feature/merge_rel21_into_develop
branch
from
bbcc023 to
ee3bbfd
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Description
All in the title.
@ashley314 This merge contains the update to the Discover site config that forces the variant
+ecflowforewok-env. We need to decide what to do. I am not sure we want to enable this across the board. System that JCSDA doesn't work with (most NOAA and NAVY systems, for example) don't need to supportewok, especially not with theecflowGUI. Is JCSDA's strategy to switch fromecflowtocylcentirely in the near future?Dependencies
Issues addressed
Working toward #1884
Applications affected
None (only site config updates)
Systems affected
Most (see site config updates)
Testing
Checklist