Summary: | add a script for crawling the baseline databases | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Dirk Pranke <dpranke> | ||||||||
Component: | New Bugs | Assignee: | Dirk Pranke <dpranke> | ||||||||
Status: | RESOLVED WONTFIX | ||||||||||
Severity: | Normal | CC: | abarth, eric | ||||||||
Priority: | P2 | ||||||||||
Version: | 528+ (Nightly build) | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Attachments: |
|
Description
Dirk Pranke
2011-07-12 19:58:50 PDT
Created attachment 100610 [details]
Patch
Created attachment 100701 [details]
fix permissions, rebaseline to HEAD
Clearing the review? flag and marking as WONTFIX ... I don't know that there's any real reason to land this. I'm not sure what this did, but OK. :) Reopening to attach new patch. Created attachment 132134 [details]
Patch
Could you give me some example usage of this command? What would I use it for? The basic idea is, for some list of ports and some list of tests, show me what the expected result is, and where we find the baselines, for each test. Options are available to filter ports and tests (e.g., all expected crashes). basically the info you get with run-webkit-tests --print trace-everything, except for the actual result, in a form amenable to human eyes and also a form amenable for further analysis/reporting, e.g., to figure out what happens if chromium-mac-leopard stops falling back to mac-leopard. In further thinking about it, i think this is probably actually two different commands (one for expectations, one for baselines). This will also replace the webkit-patch skipped-files command, which is a subset of this information. |