Skip to content
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 ESMF to 8.6.1 and dependecies #52

Open
wants to merge 1 commit into
base: noresm
Choose a base branch
from

Conversation

mvdebolskiy
Copy link
Collaborator

@mvdebolskiy mvdebolskiy commented Nov 26, 2024

Updated ESMF from 8.4.2 to 8.6.1 and PIO to 2.6.3 (includes a bug fix for 2.6.2).
All dependecies are built with iomkl-iomi/2023b, modules do not have internal dependency conflicts.

Tested with noresm2_5_alpha08b:

PASS ERS_Ld5.ne30pg3_tn14.N1850fates-sp.betzy_intel.allactive-defaultio CREATE_NEWCASE
PASS ERS_Ld5.ne30pg3_tn14.N1850fates-sp.betzy_intel.allactive-defaultio XML
PASS ERS_Ld5.ne30pg3_tn14.N1850fates-sp.betzy_intel.allactive-defaultio SETUP
PASS ERS_Ld5.ne30pg3_tn14.N1850fates-sp.betzy_intel.allactive-defaultio SHAREDLIB_BUILD time=366
PASS ERS_Ld5.ne30pg3_tn14.N1850fates-sp.betzy_intel.allactive-defaultio MODEL_BUILD time=496
PASS ERS_Ld5.ne30pg3_tn14.N1850fates-sp.betzy_intel.allactive-defaultio SUBMIT
PASS ERS_Ld5.ne30pg3_tn14.N1850fates-sp.betzy_intel.allactive-defaultio RUN time=1064
PASS ERS_Ld5.ne30pg3_tn14.N1850fates-sp.betzy_intel.allactive-defaultio COMPARE_base_rest
PASS ERS_Ld5.ne30pg3_tn14.N1850fates-sp.betzy_intel.allactive-defaultio MEMLEAK insufficient data for memleak test
PASS ERS_Ld5.ne30pg3_tn14.N1850fates-sp.betzy_intel.allactive-defaultio SHORT_TERM_ARCHIVER

@mvdebolskiy mvdebolskiy requested a review from mvertens November 26, 2024 11:53
Copy link
Collaborator

@mvertens mvertens left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks so much for this.

@mvdebolskiy
Copy link
Collaborator Author

@mvertens Can you run a full test-suite (also, probably CAM-tests?) with the new CMEPS and my branch in this PR? I am not eager to merge it, since there might be need to rebuild things if the new CMEPS is behaving weirdly.

@mvertens
Copy link
Collaborator

@mvdebolskiy - yes I will do that before this is merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants