Versions Compared

Old Version 9

changes.mady.by.user Robert Jacob

Saved on

compared with

New Version 10

changes.mady.by.user Robert Jacob

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
A test launched by the CIME Case Control System "create_test" script goes through all the phases of configuring, building and running a case.   Each phase is checked for a PASS/FAIL condition and the results are output in the TestStatus.log file in the case directory.   Within the E3SM nightly test system, the TestStatus.log for each test is uploaded to cdash is parsed in order to populate the cdash display with pass/fail and also uploaded to the dashboard for examination.


Code Block
PASS ERS.f09_g16_g.MPASLISIA.melvin_gnu CREATE_NEWCASE
PASS ERS.f09_g16_g.MPASLISIA.melvin_gnu SETUP
PASS ERS.f09_g16_g.MPASLISIA.melvin_gnu SHAREDLIB_BUILD time=164
PASS ERS.f09_g16_g.MPASLISIA.melvin_gnu NLCOMP
PASS ERS.f09_g16_g.MPASLISIA.melvin_gnu MODEL_BUILD time=95
PASS ERS.f09_g16_g.MPASLISIA.melvin_gnu SUBMIT
PASS ERS.f09_g16_g.MPASLISIA.melvin_gnu RUN time=17
PASS ERS.f09_g16_g.MPASLISIA.melvin_gnu COMPARE_base_rest
PASS ERS.f09_g16_g.MPASLISIA.melvin_gnu BASELINE
PASS ERS.f09_g16_g.MPASLISIA.melvin_gnu MEMCOMP
PASS ERS.f09_g16_g.MPASLISIA.melvin_gnu TPUTCOMP
PASS ERS.f09_g16_g.MPASLISIA.melvin_gnu MEMLEAK


...

FAIL message

FAIL meaningSettingControl
ERROR: BUILD FAIL: build e3sm failed, cat 'filename'
MODEL_BUILD FAILED for test 'testname'
Model failed to build.  Could be a code error, or compiler error or compiler license may not be available at that time.  Could run out of disk to store build artifacts.  Linking error also possible.Always onAlways on
RUN FAILED for test 'testname'
The "run phase" of the test failed.  This almost always means the executable exited early for some reason.   It could be a code error or a rea/write problem. It could also mean that data needed by check_input_data did not all download.Always onAlways on

memleak detected, memory went from X to Y in Z days
(note that this will cause the test to fail even though the word "FAIL" does not appear in the message".

The driver computes a highwater memory mark and outputs it to the coupler log each simulated day.  The log is parsed and if the highwater memory increased by more then TEST_MEMLEAK_TOLERANCE the test will fail.Always onTurn off by adding --ignore-memleak to create_test.  TEST_MEMLEAK_TOLERANCE is defined per machine in config_machines.xml.  Can be changed in testcase directory with xmlchange.

...