ExpectedTestFails.xml

<?xml version= "1.0"?>

<expectedFails version="1.1">

  <!-- Notes about the format of this file:

       The required elements for a given failure are just:

         <test name="...">
           <phase name="...">
             <status>...</status>
           </phase>
         </test>

       There can be multiple phase blocks in a given test block.

       In addition, a number of optional elements are allowed, which
       currently are just for human consumption (not parsed by any
       scripts):

       - A phase block can contain an "issue" element, which gives the
       issue number associated with this failure. (#123 refers to issue
       #123 in the ESCOMP/ctsm repository. Issues in other repositories
       should be specified as ORG/repo#123 - e.g., ESMCI/cime#123.)

       - A phase block can contain a "comment" element, which gives any
       sort of comment you desire.
  -->


  <!-- aux_clm test suite failures -->

  <test name="SMS_D.f10_f10_mg37.I2000Clm51BgcCrop.cheyenne_nvhpc.clm-crop">
    <phase name="RUN">
      <status>FAIL</status>
      <issue>#1733</issue>
    </phase>
  </test>

  <test name="SMS_D_Ld1_PS.f09_g17.I1850Clm50BgcSpinup.cheyenne_intel.clm-cplhist">
    <phase name="RUN">
      <status>FAIL</status>
      <issue>#1844</issue>
    </phase>
  </test>

  <!-- fates test suite failures -->

  <test name="ERS_D_Lm12.1x1_brazil.I2000Clm50FatesCruGs.cheyenne_intel.clm-FatesFireLightningPopDens">
    <phase name="COMPARE_base_rest">
      <status>FAIL</status>
      <issue>#667</issue>
    </phase>
  </test>

</expectedFails>