Bug 72079
| Summary: | Implement webkit-patch print-expectations | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Andrew Scherkus <scherkus> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | abarth, dpranke, ojan, tony |
| Priority: | P2 | Keywords: | NRWT |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Andrew Scherkus
Split off from https://bugs.webkit.org/show_bug.cgi?id=72001
"""
We could also build up better tools for explaining what tests run where and what the expectations are. It is actually possible to extract that from NRWT now given the appropriate command line flags, but it's not easy to do so (using the --print trace* options)
Maybe we need a "webkit-patch print-expectations" command that duplicates what we print with --print trace and iterates over all of the ports or something?
"""
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Tony Chang
I think this would be more useful in either the flakiness dashboard or garden-o-matic. In practice, you only ask the question "What are the expectations for test foo?" in the context of looking at a failure on the waterfall or on garden-o-matic.
Dirk Pranke
I won't argue that this would be useful in a web page somewhere, but I at least ask this question from the command line from time-to-time as well.
Dirk Pranke
This was fixed in bug 83347 and 83348 (two commands, print-expectations and print-baselines).