Bug 82772
| Summary: | Testers should show which rev they tested in the waterfall header | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Simon Fraser (smfr) <simon.fraser> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | mrowe, rniwa, simon.fraser |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Simon Fraser (smfr)
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Ryosuke Niwa
(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.
Ryosuke Niwa
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.