- From: Ben Kelly <web-platform-tests-notifications@w3.org>
- Date: Wed, 06 May 2015 00:47:30 GMT
- To: public-web-platform-tests-notifications@w3.org
...y in automation. We are seeing test timeouts in a number of these tests in automation. For example: https://bugzilla.mozilla.org/show_bug.cgi?id=1161055 https://bugzilla.mozilla.org/show_bug.cgi?id=1160389 Increasing the timeout to long seems to avoid these failures: https://treeherder.mozilla.org/#/jobs?repo=try&revision=3ee720899303 Note, the failures in cache-match.https.html in that run are likely due to a different, legitimate problem in gecko. I think using a long timeout for all Cache API tests is reasonable since performance will be quite variable in automated tests due to disk performance on things like AWS. View on GitHub: https://github.com/w3c/web-platform-tests/pull/1809
Received on Wednesday, 6 May 2015 00:47:37 UTC