Bug 141913 - run-webkit-tests --new-baseline should not write new result (or delete existing result) if upstream results match
Summary: run-webkit-tests --new-baseline should not write new result (or delete existi...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-23 10:32 PST by David Kilzer (:ddkilzer)
Modified: 2015-02-23 10:36 PST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Kilzer (:ddkilzer) 2015-02-23 10:32:15 PST
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.