Add expected fails file now that we have an expected fail for MOSART

cime_config/testdefs/ExpectedTestFails.xml

@@ -0,0 +1,37 @@
+<?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.
+  -->
+
+  <test name="SMS_D_Ld5.f10_f10_mg37.I1850Clm60Sp.derecho_nvhpc.mosart-default">
+    <phase name="SHAREDLIB_BUILD">
+      <status>FAIL</status>
+      <issue>MOSART#109</issue>
+    </phase>
+  </test>
+
+</expectedFails>

docs/ChangeLog

@@ -8,7 +8,7 @@ Add timestamps to rpointer files, initialize curr date from driver and compare
 to what is in the restart files (instead of initializing from restart files).
 
 Testing: standard testing (ekluzek)
-  izumi ---- ?
+  izumi ---- OK (but problems with baseline compare)
   derecho -- OK
 
 ===============================================================