...
- The "Site" column is the machine where the tests ran
- The "Build Name" column is the name of the build and should be in the format <acme_test_suite_name>_<branch>_<compiler>, e.g. acme_developer_master_gnu
- The Update, Configure and Build columns can be ignored for us at this time
- The "Test" column is where things get interesting for us, it is split into three sub-columns:
- Not Run - For us, this is a misnomer. We put tests in Not Run if the only thing wrong with them is a namelist diff
- Fail - This is the worst result for a test. Could mean: failed to build, failed during run, or a non-BFB change in results
- Pass - The test is in good shape
- The "Build Time" column is the time when the test finished.
There are many clickable items in the dashboard, the most useful is usually to click the number under the "Test" column of the tests you want to see (usually failing tests are the most interesting to probe, so you'd click the number in the "Fail" sub-column). This will take you to a page with some data about the test run at the top and a list of tests that had a specific result. The most useful data at the top of the page is the "OS Version". This is another field we hijacked to display information that is more useful to us; in this case, we use it to show the sha1 of the commit that was tested. Below the general information is a list of tests, and again, there are many clickable items. The most useful clickable item for a test is it's Status field; click this will take you to the TestStatus.out data for this test which should help to give you some clue as to what happened.
...