Currently fetch-frame-resource.https.html uses a setTimeout of 10 seconds in order to detect that a page load failed (the failure page is considered cross-origin by some browsers, so timeout was needed). Therefore the lower bound of the test completing is 10 seconds. This seems long. Chromium's default test timeout is 6 seconds for Release builds. The timeout was originally 1 second [here](https://codereview.chromium.org/621003002/), then moved to 5 seconds [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1187722) and then 10 seconds [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1213119). I could mark this as a Slow test, but am a bit reluctant and would like the test to be faster. I'm wondering if anything's changed in Mozilla's infra recently that means we might be able to explore returning the timeout to 1 second? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1194
Received on Wednesday, 13 September 2017 04:31:25 UTC