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

GEOSgcm MAPL3 Run Failure with Intel (2023-Jul-28) #2263

Closed
mathomp4 opened this issue Jul 28, 2023 · 1 comment
Closed

GEOSgcm MAPL3 Run Failure with Intel (2023-Jul-28) #2263

mathomp4 opened this issue Jul 28, 2023 · 1 comment
Assignees
Labels
🪲 Bugfix This fixes a bug!

Comments

@mathomp4
Copy link
Member

Runs of GEOSgcm MAPL3 with Intel are failing with what seem to be a LOT of surface like unsatisfied imports:

$ rg 'In ExtData resource file' AGCM_MAPL3DEBUG/c24_O1_GOCART/CURRENT/run/1day/slurm-20023972.out | uniq
        EXTDATA: ERROR: In ExtData resource file, could not find: CMATM
        EXTDATA: ERROR: In ExtData resource file, could not find: CQATM
        EXTDATA: ERROR: In ExtData resource file, could not find: CTATM
        EXTDATA: ERROR: In ExtData resource file, could not find: DFNIR
        EXTDATA: ERROR: In ExtData resource file, could not find: DFPAR
        EXTDATA: ERROR: In ExtData resource file, could not find: DFUVR
        EXTDATA: ERROR: In ExtData resource file, could not find: DISCHARGE
        EXTDATA: ERROR: In ExtData resource file, could not find: DRNIR
        EXTDATA: ERROR: In ExtData resource file, could not find: DRPAR
        EXTDATA: ERROR: In ExtData resource file, could not find: DRUVR
        EXTDATA: ERROR: In ExtData resource file, could not find: FRACICE
        EXTDATA: ERROR: In ExtData resource file, could not find: KPAR
        EXTDATA: ERROR: In ExtData resource file, could not find: QHATM
        EXTDATA: ERROR: In ExtData resource file, could not find: SS_FOUND
        EXTDATA: ERROR: In ExtData resource file, could not find: TAUXBOT
        EXTDATA: ERROR: In ExtData resource file, could not find: TAUYBOT
        EXTDATA: ERROR: In ExtData resource file, could not find: TFREEZE
        EXTDATA: ERROR: In ExtData resource file, could not find: THATM
        EXTDATA: ERROR: In ExtData resource file, could not find: TS_FOUND
        EXTDATA: ERROR: In ExtData resource file, could not find: UHATM
        EXTDATA: ERROR: In ExtData resource file, could not find: UI
        EXTDATA: ERROR: In ExtData resource file, could not find: UU
        EXTDATA: ERROR: In ExtData resource file, could not find: UUA
        EXTDATA: ERROR: In ExtData resource file, could not find: UWINDLMTILE
        EXTDATA: ERROR: In ExtData resource file, could not find: VHATM
        EXTDATA: ERROR: In ExtData resource file, could not find: VVA
        EXTDATA: ERROR: In ExtData resource file, could not find: VW
        EXTDATA: ERROR: In ExtData resource file, could not find: VWINDLMTILE

and then:

pe=00000 FAIL at line=00367    ExtDataGridCompNG.F90                    <Unsatisfied imports in ExtData>
pe=00000 FAIL at line=01670    MAPL_Generic.F90                         <status=1>
pe=00000 FAIL at line=00912    MAPL_CapGridComp.F90                     <status=1>
pe=00000 FAIL at line=00764    MAPL_CapGridComp.F90                     <status=1>
pe=00000 FAIL at line=01043    MAPL_CapGridComp.F90                     <status=1>
pe=00000 FAIL at line=00312    MAPL_Cap.F90                             <status=1>
pe=00000 FAIL at line=00258    MAPL_Cap.F90                             <status=1>
pe=00000 FAIL at line=00194    MAPL_Cap.F90                             <status=1>
pe=00000 FAIL at line=00171    MAPL_Cap.F90                             <status=1>
pe=00000 FAIL at line=00031    GEOSgcm.F90                              <status=1>

Our first thought is somehow maybe GEOS-ESM/GEOSgcm_GridComp#772 from @zhaobin74 did something? It does add/change qualified TerminateImport calls.

But the thing is MAPL2 does not have any issues! Only MAPL3. And as far as we know, MAPL2 and MAPL3 are the same when it comes to import termination code!

It is also possible that solving this will solve #2262 as that too points to import termination code.

@mathomp4
Copy link
Member Author

Close in favor of #2264

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🪲 Bugfix This fixes a bug!
Projects
None yet
Development

No branches or pull requests

2 participants