Open worleyph opened 3 years ago
Assigned to @rljacob for reassignment to appropriate personnel, if it is in fact important that maint-1.2 run on compy.
@rljacob @worleyph I am able to successfully run a case (FC5AVIC-L and ne4_ne4) using maint-1.2 branch on Compy with the following changes.
I will do more testing with other cases as well. Is this what we are looking for?
@bibiraju , sounds right to me. I'd like to try your update myself, just to check that the performance archiving logic is working correctly. Do you have a branch that I could check out, or can you point me at your sandbox?
@rljacob , is there a test suite for the maint branches that @bibiraju can use to verify correctness?
@worleyph here's my branch bibiraju/maint-1.2/compy https://github.com/E3SM-Project/E3SM/tree/bibiraju/maint-1.2/compy
e3sm-developer should work on maint-1.2.
@bibiraju yes you are on the right track. You just need to backport the compy settings from master to maint-1.2.
@bibiraju , repeated the same F case and also worked for me. Looked closely at performance archiving logic, including checkpointing, and it is all working fine. Thanks!
e3sm-developer should work on maint-1.2.
@bibiraju yes you are on the right track. You just need to backport the compy settings from master to maint-1.2.
@rljacob should I match the master branch or maint-1.0?
master.
@rljacob , does that mean that maint-1.0 and maint-1.1 should (eventually) be resynced to master? A lot has changed in the CIME layer since then.
No we never actually merge master to the maint branches. But the latest settings for compy from master should be on the maint branches (ported by hand).
@bibiraju and @rljacob , can this be closed?
@rljacob indicated that all maint tags should work on all supported systems. On compy using maint-1.2,
In contrast,