Page Comparison

...

• 1. cd ACME/cime/scripts-acme
  2. ./create_test test_suite -testid test_label -testroot test_root_dirsuite [--compiler compiler --baseline-rootacme_baseline_dir -testid t test_label -r test_root_dir] [-(comparec|generateg) [-b baseline_subdir ]] [--project project_or_account ]
     
     1. machine - The ACME scripts will probe your machine name for the machine that you're on, all lowercase, look here for supported machinesfrom the current nodename
     2. compiler - The compiler toolset you wish to use, examples are: gnu, intel, pgi. You do not need to provide this if you want the default compiler (the first compiler listed in the COMPILERS parameter for your machine)
     3. test_suite - The name of the test category you want to run, like acme_developer. You can also provide a list of test names.
     4. testroot - The path where your test cases will be dumped. Default will be CESMSCRATCHROOT
     5. acme_baseline_dir - You only need to specify this if you want to use a different baseline area than is specified in <ACME>/scripts/ccsm_utils/Machines/config_machines.xml for your machinefor your machine by the CCSM_BASELINE parameter
     6. -c/-g - Do a baseline comparison/generation. You do not have to do any baseline operations.
     7. baseline_subdir - The name of the baselines (usually the major release you're on) you want to use. Use -generate if this is the first time running this test on this machine OR if you want to regenerate baseline results for this test (approved BFB change); otherwise, always use -compareThe default will be <compiler>/<current-branch-name>. Don't bother with this option unless you provided -c or -g.
     8. project_or_account - The id that lets you run batch jobs on this machine
  3. Once the tests are running, you'll want to see test results
     1. Case 1: Simple
        
        1. cd test_root_dir
        2. you will find a script named cs.status.(testid).(machine) . You can run this script from the test root directory to see the status of tests being run within this suite
     2. Case 2: We have a more sophisticated script called wait_for_tests that provides extra capabilites like: waiting for tests to finish, converting results to CTest and submitting to a CDash dashboard
        
        1. cd test_root_dir
        2. <ACME>/scripts/acme/wait_for_tests [ -d buildname] */TestStatus
  4. Example: to run the 'acme_developer' suite on Edison using the Intel compiler (assuming everything has been set up and this is not the first run), you would run:
     1. cd ACME/cime/scripts-acme
     2. ./create_test -xml_mach edison -xml_compiler intel -xml_category acme_developer -testid t acme_dev -testroot r $SCRATCH/acme_dev -c -compare b v0.1 -project acme
     3. cd $SCRATCH/acme_dev
     4. ./cs.status.acme_dev.edison

See Interpreting test results.

...