- From: jugglinmike <web-platform-tests-notifications@w3.org>
- Date: Wed, 05 Apr 2017 22:59:21 GMT
- To: public-web-platform-tests-notifications@w3.org
The log for the failed job shows that the tests were run for seven of the ten iterations before the automation ultimately timed out. Since testhardness.js accounts for timeouts, I don't think this reflects a problem in the JavaScript runtime itself. I've checked out this commit and run the "check stability" script locally, but I was unable to reproduce the timeout. This means the issue may be due to a race condition, and that the build could be made to pass by simply scheduling another execution of this job. That's obviously not a long term fix, but assuming it works at all, it will at least unblock you for now, @annevk. In case you decide to try that, I'll leave a link to the failed job for forensics purposes: https://travis-ci.org/w3c/web-platform-tests/jobs/219002365 View on GitHub: https://github.com/w3c/web-platform-tests/pull/5389#issuecomment-292021205
Received on Wednesday, 5 April 2017 22:59:33 UTC