-
Notifications
You must be signed in to change notification settings - Fork 371
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
add eamxx tests to e3sm suites #6640
Conversation
|
9d1f604
to
956af5d
Compare
@mahf708 is this ready? |
yes, we may run into issues once this is on next, but as far as I am concerned, these tests should be passing on all our machines. I will debug if they fail |
Question: should we add some/all of the tests that are currently in the various "e3sm_scream" suites to our nightly testing? |
Personally, that's my ultimate goal. I wanted to start with these tests because they are more "traditional" and designed piece by piece with your involvement (in PRs here in this repo). I am happy to add more tests to this PR or issue a separate PR later. I would like @jgfouca and @AaronDonahue to weigh in and see what they prefer :) |
Adding more test can wait but I think you should create new suite names in preparation for that. The "atm" suites are really EAM suites. It shouldn't be necessary for an EAM developer to make EAMxx tests pass. (Or should it?). So maybe you should make new e3sm_eamxx_developer, e3sm_eamxx_integration, and e3sm_eamxx_prod suites, add the tests you've already added to those, and then include them in the corresponding e3sm full suites. |
Recall COSP edits led to EAMxx breaking, so at least one test should be run under atm developer. I also thought we were slowly move "atm" from EAM to EAMxx, no? |
Good point. If EAMxx depends on code in components/eam then we need an eamxx test. That transition will take years but we need to build up our eamxx testing soon. But new suites can also wait for another PR. |
Adds EAMxx tests to e3sm_atm_developer, e3sm_atm_integration, and e3sm_atm_prod.
I looked at the errors and I list them below. I think there's some setting HOMME isn't happy with on chrysalis (so it aborts). There's a fail in PIO on pm-cpu that looks like a fluke. There are fails about "too many mpi tasks" on pm-cpu that I have never seen... Any advice on how to proceed? copying @ndkeen DIFF:
FAIL: SMS_D_Ln5.ne4pg2_oQU480.F2010-SCREAMv1-MPASSI.chrysalis_intel (run)
SMS_D_Ln5.ne4pg2_oQU480.F2010-SCREAMv1-MPASSI.chrysalis_intel
ERS_Ld5.ne4pg2_oQU480.F2010-SCREAMv1-MPASSI.chrysalis_intel.eamxx-prod (run)
ERS_Ld5.ne4pg2_oQU480.F2010-SCREAMv1-MPASSI.chrysalis_intel.eamxx-prod
SMS_D_Ln5.ne4pg2_oQU480.F2010-SCREAMv1-MPASSI.pm-cpu_nvidia (build)
SMS_D_Ln5.ne4pg2_oQU480.F2010-SCREAMv1-MPASSI.pm-cpu_nvidia
SMS_Ld1.ne30pg2_ne30pg2.F2010-SCREAMv1.pm-cpu_intel.eamxx-prod (run)
SMS_Ld1.ne30pg2_ne30pg2.F2010-SCREAMv1.pm-cpu_intel.eamxx-prod
ERS_Ld5.ne4pg2_oQU480.F2010-SCREAMv1-MPASSI.pm-cpu_intel.eamxx-prod + SMS_D_Ln5.ne4pg2_oQU480.F2010-SCREAMv1-MPASSI.pm-cpu_gnu (run)
ERS_Ld5.ne4pg2_oQU480.F2010-SCREAMv1-MPASSI.pm-cpu_intel.eamxx-prod SMS_D_Ln5.ne4pg2_oQU480.F2010-SCREAMv1-MPASSI.pm-cpu_gnu
|
maybe @oksanaguba can help with the HOMME errors on chrysalis. |
I propose we wait to bring in this PR until the SCREAM and E3SM repos are unified. The problem right now is the EAMxx code in E3SM is out of date w.r.t. the SCREAM repo. Thus, it's unclear what is being tested. In addition, it's possible fixes would require coordination between repos. If these specific tests should be exercised immediately, I recommend adding them to the SCREAM-repo nightlies so they have a better chance of running out of the box when the repos get unified. |
Just quickly: for the fail with too many MPI procs, this is a known issue with homme in scream. There is code not wanting to go forward if num npi's larger than numelem. |
i agree with Andrew that it would be better to wait till repos are merged together. |
Not actually reverted after a force push. See how it does with #6675 |
Thanks everyone for your patience and advice. Closing this PR for now, and I will work on a different PR in the future if needed. (I will make a separate PR for edits related to the github actions workflows.) |
Adds EAMxx tests to e3sm_atm_developer, e3sm_atm_integration, and e3sm_atm_prod.