...
For this example, we setup a test for GR v17r35p20. The package is GlastRelease, the version name we choose is v17r35p20, and we are running all the tests, AllGamma, BackGndMixDC2, VerticalGamma100MeV, VerticalProton1GeV, etc. We want the default comparison to be to version name, v15r47p12gr11.
Panel | ||
---|---|---|
| ||
Log into a machine with access to the batch farm. |
Panel | ||||
---|---|---|---|---|
| file
| |||
packag GlastRelease |
Now run the tests. These will be submitted to the batch queue.
Panel | ||
---|---|---|
| ||
> $SYSTESTS/src/exec/runSysTests.sh |
...
You will see lots of console output, but the jobs are submitted to the batch queue and do not require you to stay logged in to the terminal. You can come back and find top level errors in the version result directory in testerr. The output files and logs will be in the test result directories, e.g., $SYSTESTS/GlastRelease/v17r35p20/<test_name>/linux/
You can check on the runs using bjobs and looking at the output files. If there is a problem with the tests or you want to end the run early, you can kill the jobs with bkill 0. It is fine to do this and start them again. A run will completely overwrite a previous run with the same version name unless you set special options in the config file.
To examine the output of the job see http://glast-ground.slac.stanford.edu/SystemTests/summary.jsp. You will see completed jobs appear there, but no histograms or comparison results until you do the next step.
Once all the runs have finished, you will need to load the histograms and results to the database for web viewing.
Panel | ||
---|---|---|
| ||
> cd $SYSTESTS/src/exec |
...