82772 2012-03-30 12:53:59 -0700 Testers should show which rev they tested in the waterfall header 2012-03-30 13:08:04 -0700 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) Unspecified Unspecified NEW P2 Normal --- 1 simon.fraser webkit-unassigned mrowe rniwa simon.fraser oldest_to_newest 592422 0 simon.fraser 2012-03-30 12:53:59 -0700 Testers often lag behind builders, so just looking at the column headers on the waterfall page can be very misleading. It would help if the column headers said which rev was tested last (and maybe some indicator of how "stale" these results are. So rather than: "failed 15 failures 6 new passes 5 flakes" it could say: "11023 (6 revs ago): failed. 15 failures 6 new passes 5 flakes". Or something. 592427 1 rniwa 2012-03-30 12:59:59 -0700 (In reply to comment #0) > Testers often lag behind builders, so just looking at the column headers on the waterfall page can be very misleading. It would help if the column headers said which rev was tested last (and maybe some indicator of how "stale" these results are. > > So rather than: > "failed 15 failures 6 new passes 5 flakes" > it could say: > "11023 (6 revs ago): failed. 15 failures 6 new passes 5 flakes". > > Or something. (6 revs ago) will be hard to do. But printing the revision number will be easy. Note this information is already shown in the update step. 592435 2 rniwa 2012-03-30 13:08:04 -0700 FYI, we just need to modify RunWebKitTests::getText2. I don't know how you'd get the revision number that triggered the build here though.