72079 2011-11-10 17:57:04 -0800 Implement webkit-patch print-expectations 2012-06-20 11:39:07 -0700 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) Unspecified Unspecified RESOLVED FIXED NRWT P2 Normal --- 1 scherkus webkit-unassigned abarth dpranke ojan tony oldest_to_newest 500448 0 scherkus 2011-11-10 17:57:04 -0800 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? """ 500864 1 tony 2011-11-11 09:50:32 -0800 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. 500985 2 dpranke 2011-11-11 11:51:25 -0800 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. 653704 3 dpranke 2012-06-20 11:39:07 -0700 This was fixed in bug 83347 and 83348 (two commands, print-expectations and print-baselines).