You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 6, 2019. It is now read-only.
Do you think it'd be worth trying more aggressive restarting
The fact that this immediately interferes with almost every "chunk" makes me think that restarting will not resolve it, but it couldn't hurt to try (especially now that we're disabling Safari on Sauce Labs). We'll see what effect this has on time-to-results (it may get ugly).
As anticipated, the results continue to be invalid. From later on in that discussion thread:
We've completed a collection from Edge that involved restarting after every test failure. This increased build time from 15 hours to 24 hours, but it had no appreciable affect on the veracity of the results.
There's little value in improving the time-to-results without fixing the underlying problem. Since the fix will itself shorten the duration to some extent, I'm going to hold off on reverting the referenced commit.
Hovering the recent runs on https://wpt.fyi/test-runs?product=edge, Edge runs have taken 20-30h.
This is probably due to 27c22db.
The text was updated successfully, but these errors were encountered: