Skip to content

Commit

Permalink
For now, remove nuopc tests with mid-year restart
Browse files Browse the repository at this point in the history
These tests die with the error:

  * FATAL ERROR : (glad_main.F90:650)  Valid_inputs cannot be .false. if trying
 to do a mass balance time step

I think this is a known limitation of CMEPS right now, but I will open
an issue to track this - and then to reinstate these tests when the
issue is fixed.
  • Loading branch information
billsacks committed Nov 30, 2020
1 parent 6dc6854 commit a66c96a
Showing 1 changed file with 0 additions and 38 deletions.
38 changes: 0 additions & 38 deletions cime_config/testdefs/testlist_cism.xml
Original file line number Diff line number Diff line change
Expand Up @@ -386,25 +386,6 @@

</machines>
</test>
<test name="ERS_Vnuopc_Lm24" grid="f10_f10_musgs" compset="I1850Clm50SpG">
<machines>

<machine name="cheyenne" compiler="intel" category="aux_glc">
<options>
<option name="wallclock">1:59</option>
<!-- 2016-10-25: At least in the ERS_Ly5 test: There is a big jump in
memory at the start of year 2. In the 5-year run, things then
stay roughly constant after that. Note that the start of year 2
is when CISM does its first prognostic solve, so I think this is
expected behavior. Thus, I believe this is not actually a
problem. -->
<option name="memleak_tolerance">0.34</option>
<option name="comment">Mid-year exact restart test</option>
</options>
</machine>

</machines>
</test>

<test name="ERI_Lm24" grid="f10_f10_musgs" compset="I1850Clm50SpG" testmods="cism/isostasy_period4">
<machines>
Expand All @@ -425,25 +406,6 @@

</machines>
</test>
<test name="ERI_Vnuopc_Lm24" grid="f10_f10_musgs" compset="I1850Clm50SpG" testmods="cism/isostasy_period4">
<machines>

<machine name="cheyenne" compiler="intel" category="aux_glc">
<options>
<option name="wallclock">1:59</option>
<!-- 2016-10-25: At least in the ERS_Ly5 test: There is a big jump in
memory at the start of year 2. In the 5-year run, things then
stay roughly constant after that. Note that the start of year 2
is when CISM does its first prognostic solve, so I think this is
expected behavior. Thus, I believe this is not actually a
problem. -->
<option name="memleak_tolerance">0.34</option>
<option name="comment">Test branching mid-year; include isostasy because there are extra subtleties with getting isostasy to restart exactly</option>
</options>
</machine>

</machines>
</test>

<test name="ERI" grid="f10_f10_musgs" compset="I1850Clm50SpG" testmods="cism/test_coupling">
<machines>
Expand Down

0 comments on commit a66c96a

Please sign in to comment.