...
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 presented in the Out-of-the-Box (OOTB) field named "OS Version." Jim Foucar configured this field to display the sha1 of the commit that was tested (it is not possible to rename the field though). 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. Clicking this will take you to the TestStatus.out data for the test, which should help to give you some clue as to what happened.
Test Diagnosis Walkthrough
Let's walk through a hypothetical situation. Tests are failing on redsky and you want to know what happened. You go to our dashboard and see this:
In the Test-Fail column of the redsky row (circled in pink) you can see that redsky has a single failing test, and this failing test is new as of the most recent run of the tests (the +1 in the upper corner indicates that it is new). Click the "1" in the red square, which will take you to this page:
The id of the commit that was tested is found in the "OS Version" field (highlighted it in pink, and recall that this field has been hijacked to present the sha1 of the commit). Click the red "Failed" link to go to the TestStatus.log for this failed test. You'll see something like this:
The data in the pink square makes it obvious that the test failed due to a non-BFB result for this test.
Getting Log Data for Failed Tests
...