[dev/gfs.v17] Module files update 1: non-gdas components to use operational modules on wcoss2#5010
Conversation
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
DavidHuber-NOAA
left a comment
There was a problem hiding this comment.
Looks good to me. Thanks for the work on this @TravisElless-NOAA!
|
I'll run a C6 case for this. |
|
All tests passed on C6: |
|
Tests on WCOSS2 will eventually pass as shown below with one caveat currently. Several arch jobs did initially fail as the node ddxfer01 does not recognize the cray-pals/1.3.2 module loaded by load modules. This leads to a couple of questions:
Thought I would bring this up here in case anyone has a preference on the way forward. But the frequency which this hit ddxfer01 means we should have a solution in place before merging |
|
Noting here that I opened a GDIT ticket and they took ddxfer01 offline for repairs. So likely don't need to make further updates in regards to that issue |
|
@TravisElless-NOAA can you resolve the conflict in run.wcoss2.ver? |
|
Should be good to go now @DavidHuber-NOAA |
Description
This PR brings updates to the v17 package to allow for the use of operational versions of module files on wcoss2. Changes are made to allow module file versions to be updated via
build.ver/run.verModule file versions included in these wcoss2 version files will be the modules used during production. Noting a future PR will be needed for the GDASApp based modules and virtual environment once those are added to the production environment.Type of change
Change characteristics
How has this been tested?
Initial tests passed on wcoss2. Will run full suite
Checklist