Stability checker frequently timing out on Chrome

[gsnedders]

17:17 < jgraham> There's some bug involving chromedriver that we don't understand where sometimes it just refuses to connect

@bobholt is apparently looking into this.

cc/ @jgraham @jugglinmike

[jugglinmike]

@bobholt is looking in to this.

[bobholt]

The relevant PRs to this issue is #5370. 5263 and 5395 are mis-attributed. The Chrome build in 5395 ran all tests to completion in Chrome and produced results. 5263 has a demonstrable error unrelated to timeouts.

The issue that distinguishes this from #5406 is that in this, Chromedriver only tries to start once on each port, but gets a notification of "No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself." at the end.

[bobholt]

Going back through PRs, all PRs since 11:15am EDT on April 7 have completed Chrome tests that match the Firefox tests. I am also no longer able to recreate the timeouts on my fork.

Unless this PR success is due to re-triggering Chrome jobs, I propose that this be closed. This is unsatisfying to me personally, because I was not able to track down a root cause for the timeouts, but as I no longer recreate the behavior, I don't hold out much hope of figuring it out.

[gsnedders]

https://travis-ci.org/w3c/web-platform-tests/jobs/223375148 is a build timing out

[jugglinmike]

@gsnedders That job seems to have completed successfully. Travis reports "Done. Your build exited with 0." and (unlike in recent cases) marks the job as "passed." I checked the other "check stability" job for the same build, and things look to be the same there. Maybe that was the wrong link?

[gsnedders]

@jugglinmike I stupidly mixed things up and hit restart on it for some reason thinking that it got a new job number. :(