[WPT auto-import] Retry some failed try jobs during import. |
||||||
Issue descriptionCurrently there are two sets of try-jobs that are tried during an import job: 1. layout test try jobs to get new expectations/baselines 2. CQ try jobs If anything in any of these try jobs goes wrong, the whole import fails. It might be worth adding some retry logic, for the first part: if layout tests don't run properly on some platform (e.g. android), that job could be retriggered. In a recent WPT import, rebaseline failed because the android job failed to run (https://codereview.chromium.org/2668783003), and *maybe* re-running on android would have enabled rebaselining to work. Fixing bug 673966 would also have helped in this case.
,
Feb 3 2017
,
Jul 3 2017
,
Jul 3 2017
,
Jul 3
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 3
I don't think the benefit of retrying justifies the engineering cost and code complexity currently. And now that we are running the importer continuously instead of just once or twice a day, it's not a huge problem. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ajha@chromium.org
, Feb 3 2017