Summary: | WebKit2 bots don't exit after 50 failures or timeouts | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Alexey Proskuryakov <ap> | ||||
Component: | Tools / Tests | Assignee: | Lucas Forschler <lforschler> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | beidson, commit-queue, lforschler, rniwa, simon.fraser | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Alexey Proskuryakov
2013-10-29 10:59:29 PDT
These are currently set to NOT abort early. Simply changing this to True should set the timeout same as the Webkit1 tests. class RunWebKit2Tests(RunWebKitTests): def start(self): self.setProperty("shouldAbortEarly", False) self.setCommand(self.command + ["--webkit-test-runner"]) return RunWebKitTests.start(self) Created attachment 215400 [details]
set shouldAbortEarly to True
Comment on attachment 215400 [details] set shouldAbortEarly to True This was changed in bug 94506, apparently because WK2 used to have lots and lots of flaky tests, so letting these run to completion still gave you some information about non-flakily failing tests. We are not there any more with respect to how horrible tests are, and allowing an unlimited number of crashes or timeouts grinds bots to a halt after a bad commit that crashes everywhere. Alternatively to landing this change, we could roll out the one from bug 94506. What do you think? I don't think we should roll out the previous one. It is nice that it adds this property. Let's keep the shouldAbortEarly property, and just set it to False with this change. That should read, set it to True :) Comment on attachment 215400 [details] set shouldAbortEarly to True Clearing flags on attachment: 215400 Committed r158207: <http://trac.webkit.org/changeset/158207> All reviewed patches have been landed. Closing bug. restarted master. This should be live. |