...
The data in the pink square (again, added by hand here) shows the id of the commit that was tested. The next logical thing is to 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
In many cases the TestStatus.log file will not have adequate information to diagnose a problem. For build and run failures, log files for the problematic test will be automatically uploaded. If results are available you'll see a gold cube next to the top-level results for a machine/compiler/branch on the main page:
The highlighted gold square indicates that log files are available to download for the acme_test_only_next_gnu build. Unzipping and untarring this file will yield a directory tree in which there is a subdirectory for each failing test that will have the relevant log files.