Summary: | new-run-webkit-tests: add a --no-retry-failures flag | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Dirk Pranke <dpranke> | ||||
Component: | Tools / Tests | Assignee: | Dirk Pranke <dpranke> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | abarth, cjerdonek, eric, ojan, tony, webkit.review.bot | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | OS X 10.5 | ||||||
Attachments: |
|
Description
Dirk Pranke
2010-04-19 18:40:26 PDT
Created attachment 53760 [details]
Patch
Comment on attachment 53760 [details]
Patch
Why do we want more options? I'm trying to cut down on the number of options the user sees so we can make --help less intimidating. These seem unlikely for a user to use.
(In reply to comment #2) > (From update of attachment 53760 [details]) > Why do we want more options? I'm trying to cut down on the number of options > the user sees so we can make --help less intimidating. These seem unlikely for > a user to use. Certainly --retry-failures is unlikely to be used, since it's the default. I would be fine if --no-retry-failures was hidden, but I'd like for it to be there, especially to help w/ unit testing coverage. Comment on attachment 53760 [details]
Patch
WebKitTools/Scripts/webkitpy/layout_tests/run_webkit_tests.py:1768
+ optparse.make_option("--no-retry-failures", action="store_false",
I thought we had magic to generate the [no-] versions.
I've not written the --no- magic yet. Committed r58183: <http://trac.webkit.org/changeset/58183> http://trac.webkit.org/changeset/58183 might have broken Qt Linux Release |