...
- Create and run the test suite as usual. See " Running the tests " page for information on how to run the test suite.
Use the wait_for_tests (CIME2CIME: <ACME<E3SM_SOURCE_DIR>/cime/scripts-acme/Tools/wait_for_tests) script to upload the results to cdash. In the case below my test results (the testroot directory) are in the testroot -anvil directory directory (<E3SM_SOURCE_DIR>/cime/scripts/testroot) and I named the cdash buildname as "jayeshe3sm_acmedeveloper_developerdqwu_mastertest_anvilpio2_gnu03_32pescori" .
[jayesh@blogin2 scripts-acme]$ ./Tools/wait_for_tests -n -b jayesh_acme_developer_master_anvil_gnu_32pes -p ACME_Climate -g ACME_Other ./testroot-anvile3sm_developer_dqwu_test_pio2_03_cori -p ACME_Climate -g Experimental ./testroot/*/TestStatus
To upload the test results to E3SM PIO cdash, use the wait_for_tests (CIME: <E3SM_SOURCE_DIR>/cime/scripts/Tools/wait_for_tests) script to upload the results. In the case below my test results (the testroot directory) are in the testroot directory (<E3SM_SOURCE_DIR>/cime/scripts/testroot) and I named the cdash buildname as "e3sm_developer_dqwu_test_pio2_03_cori" .The test results are uploaded to E3SM PIO cdash dashboard (corresponds to "-p ACME_PIO"). The results are uploaded to a section in the cdash dashboard named "Experimental" (corresponds to "-g Experimental").
[jayesh@blogin2 scripts]$ ./Tools/wait_for_tests -n -b e3sm_developer_dqwu_test_pio2_03_cori -p ACME_PIO -g Experimental ./testroot/*/TestStatus