PASS ERS.f09_g16_g.MPASLISIA.melvin_gnu CREATE_NEWCASE PASS ERS.f09_g16_g.MPASLISIA.melvin_gnu XML 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
Briefly, PASS means the test passed, FAIL means that it failed and PEND means the test is waiting to be run or currently running.
The following table, assembled from the Automated Test System slides presented by CSEG, describes the result codes of tests that have passed, failed, or are still running.
| Result Code | Meaning | Where to Look First |
|---|---|---|
| Good results | ||
| PASS | Test passed | |
| Bad results | ||
| FAIL | Test failed (either due to run failure or, e.g., no-exact restarts for an ERS test) | (1) TestStatus.out file in case directory: this will help you see the cause of failure – e.g., run didn’t complete vs. test requirements (such as exact restart) weren’t met. Look for FAIL in this file, and any messages above the FAIL line. (2) If run didn’t complete, check log files and core files in run directory (3) If requirements of test weren’t met,TestStatus.out will generally refer to differences in coupler log files and/or coupler history files. History file differences can be seen in the cprnc.out file in the run directory. |
| Test not yet complete | ||
| PEND | Test submitted, waiting in queue, or currently running | |