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
I'll start by admitting that this problem arose due to user error on my part: I accidentally set up a case where I set ./xmlchange REST_OPTION=nmonths,REST_N=18,RESUBMIT=1, but I forgot to increase HIST_OPTION and HIST_N. So it ran for 5 days, and didn't create any restart files in that time. But I think the same problem would occur if you intentionally ran a case without restart files, e.g., by setting REST_OPTION=never.
When the short-term archiver ran in this case, it generated the message,
Setting resource.RLIMIT_STACK to -1 from (-1, -1)
st_archive starting
moving /glade/scratch/sacks/i.e20.I1850Clm50Sp.f10_f10_musgs.001r/run/rof.log.7635249.chadmin1.180417-123429.gz to /glade/scratch/sacks/archive/i.e20.I1850Clm50Sp.f10_f10_musgs.001r/logs/rof.log.7635249.chadmin1.180417-123429.gz
moving /glade/scratch/sacks/i.e20.I1850Clm50Sp.f10_f10_musgs.001r/run/cesm.log.7635249.chadmin1.180417-123429.gz to /glade/scratch/sacks/archive/i.e20.I1850Clm50Sp.f10_f10_musgs.001r/logs/cesm.log.7635249.chadmin1.180417-123429.gz
moving /glade/scratch/sacks/i.e20.I1850Clm50Sp.f10_f10_musgs.001r/run/cpl.log.7635249.chadmin1.180417-123429.gz to /glade/scratch/sacks/archive/i.e20.I1850Clm50Sp.f10_f10_musgs.001r/logs/cpl.log.7635249.chadmin1.180417-123429.gz
moving /glade/scratch/sacks/i.e20.I1850Clm50Sp.f10_f10_musgs.001r/run/lnd.log.7635249.chadmin1.180417-123429.gz to /glade/scratch/sacks/archive/i.e20.I1850Clm50Sp.f10_f10_musgs.001r/logs/lnd.log.7635249.chadmin1.180417-123429.gz
moving /glade/scratch/sacks/i.e20.I1850Clm50Sp.f10_f10_musgs.001r/run/atm.log.7635249.chadmin1.180417-123429.gz to /glade/scratch/sacks/archive/i.e20.I1850Clm50Sp.f10_f10_musgs.001r/logs/atm.log.7635249.chadmin1.180417-123429.gz
ERROR: Cannot find a i.e20.I1850Clm50Sp.f10_f10_musgs.001r.cpl*.r.*.nc file in directory /glade/scratch/sacks/i.e20.I1850Clm50Sp.f10_f10_musgs.001r/run
It looks like this is generated from the _get_datenames function.
Shouldn't it be possible to run the short-term archiver even if there are no restart files present?
The text was updated successfully, but these errors were encountered:
…(PR #2480)
Big update to wait_for_tests/jenkins
Changes:
* Upgrade cdash XML spoofing for prettier cdash pages for e3sm
* Add ability for jenkins jobs to use alternate baseline area, nice for test cleanup
* New test test suite that includes DIFFs
* Add ability to turn off all test teardowns from scripts_regr command line
* New Jenkins test to upload a realistic dashboard result
* Make TESTBUILDFAIL produce a bldlog file (So that uploading of log files for failed builds can be tested)
* Add logging to TestStatus processing (waiting)
[BFB]
* jgfouca/cime/upgrade_wait_for_tests_cdash:
Make pylint happy
Remove useless commented-out code
Make TESTBUILDFAIL produce a bldlog file
Big update to wait_for_test/jenkins
wait_for_test logging working
Remove debug stuff
Progress
I'll start by admitting that this problem arose due to user error on my part: I accidentally set up a case where I set
./xmlchange REST_OPTION=nmonths,REST_N=18,RESUBMIT=1
, but I forgot to increase HIST_OPTION and HIST_N. So it ran for 5 days, and didn't create any restart files in that time. But I think the same problem would occur if you intentionally ran a case without restart files, e.g., by setting REST_OPTION=never.When the short-term archiver ran in this case, it generated the message,
It looks like this is generated from the
_get_datenames
function.Shouldn't it be possible to run the short-term archiver even if there are no restart files present?
The text was updated successfully, but these errors were encountered: