Bug 141913
| Summary: | run-webkit-tests --new-baseline should not write new result (or delete existing result) if upstream results match | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | David Kilzer (:ddkilzer) <ddkilzer> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ap, dbates, simon.fraser |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
David Kilzer (:ddkilzer)
The most annoying thing ever about `run-webkit-tests --new-baseline` is that it writes results even if upstream results match.
We should fix it to do the following:
- Only write new result if the upstream result doesn't match.
- Delete existing result if new result matches upstream result.
See also Bug 47293 about runtime warnings when new "failing" port-specific result matches upstream result.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |