You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at some of my recent regression tests for ctsm-fates and comparing them to some regression tests on e3sm-fates, I noticed that the MEMLEAK check is returning "Insufficient data for memleak test" for ctsm-fates tests. After some guidance from @billsacks and @ekluzek, I took a look at the system_tests_common.py code and noticed that the _cpllog appears to be defined as drv for nuopc cases. Looking at the log files from the ctsm-fates runs, I don't see much in the drv.log, but I do see a bunch of memory reporting in med.log. Is this correct or is there something that changed since commit 4376e62?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Looking at some of my recent regression tests for ctsm-fates and comparing them to some regression tests on e3sm-fates, I noticed that the
MEMLEAK
check is returning "Insufficient data for memleak test" for ctsm-fates tests. After some guidance from @billsacks and @ekluzek, I took a look at the system_tests_common.py code and noticed that the_cpllog
appears to be defined asdrv
for nuopc cases. Looking at the log files from the ctsm-fates runs, I don't see much in the drv.log, but I do see a bunch of memory reporting in med.log. Is this correct or is there something that changed since commit 4376e62?Beta Was this translation helpful? Give feedback.
All reactions