Updated ChangeLog

doc/ChangeLog

@@ -1,7 +1,7 @@
 ===============================================================
 Tag name:  ctsm5.1.dev048
 Originator(s):  slevis (Samuel Levis,SLevis Consulting,303-665-1310)
-Date:  Fri Jul 09 11:32:57 MDT 2021
+Date:  Fri Jul 09 17:51:57 MDT 2021
 One-line Summary: Make certain history fields descriptive inst. of labeling by number
 
 Purpose and description of changes
@@ -41,67 +41,21 @@ Caveats for users (e.g., need to interpolate initial conditions):
  in place of using numbers to differentiate them.
 
 Substantial timing or memory changes:
-[For timing changes, you should at least check the PFS test in the test suite]
+ The PFS test PASSes but
+ TPUTCOMP non-passes: 4
+ MEMCOMP non-passes: 25
+ on Cheyenne
 
 
 Testing summary:
 ----------------
-[... Remove before making master tag.
-
-Nearly all CTSM tags should undergo 'regular' (aux_clm) testing.
-However, it occasionally makes sense to do more or less system testing;
-here is guidance on different available levels of system testing:
-    a) no system testing (for use when the only changes are ones that
-                          have absolutely no impact on system runs; this
-                          includes documentation-only tags, tags that
-                          just change the tools or some python code that
-                          does not impact system runs, etc.)
-    b) minimal (for use in rare cases where only a small change with 
-                known behavior is added ... eg. a minor bug fix. This
-		might be to just run the "short" test list, or to run
-		a single test. Whatever makes sense for the particular case.)
-    c) regular (regular tests on normal machines if CTSM source is modified)
-    d) release (regular tests plus the fates, ctsm_sci, mosart and rtm test lists
-                and normally all of the ancillary tests (build-namelist, python, ptclm, etc.) 
-		would be run as well)
-
-In addition, various other tests of the tools, python and perl
-infrastructure should be run when appropriate, as described below.
-
-...]
-
-[Remove any lines that don't apply.]
 
  [PASS means all tests PASS; OK means tests PASS other than expected fails.]
 
-  build-namelist tests (if CLMBuildNamelist.pm has changed):
-
-    cheyenne - 
-
-  tools-tests (test/tools) (if tools have been changed):
-
-    cheyenne - 
-
-  PTCLM testing (tools/shared/PTCLM/test): (if cime or cime_config are changed)
-  (PTCLM is being deprecated, so we only expect this to be done on occasion)
-
-    cheyenne - 
-
-  python testing (if python code has changed; see instructions in python/README.md; document testing done):
-
-    (any machine) - 
-
   regular tests (aux_clm: https://github.com/ESCOMP/CTSM/wiki/System-Testing-Guide#pre-merge-system-testing):
 
     cheyenne ---- OK
     izumi ------- OK
-
-  fates tests:
-    cheyenne ---- 
-
-  any other testing (give details below):
-
-If the tag used for baseline comparisons was NOT the previous tag, note that here:
 
 
 Answer changes