REFTEST TEST-UNEXPECTED-FAIL | file:///e:/builds/moz2_slave/mozilla-central-win32-unittest/build/content/base/crashtests/458637-1.html | timed out waiting for onload to fire REFTEST TEST-UNEXPECTED-FAIL | file:///e:/builds/moz2_slave/mozilla-central-win32-unittest/build/content/canvas/crashtests/421715-1.html | timed out waiting for onload to fire These have been occurring frequently on Windows trunk for the last week. They always occur together. This behaviour started on 1a4e256b6894 although 458637-1.html seems to have timed out at least once before then (although definitely a lot less often). Likewise, I only see one isolated timeout of 458637-1.html on the 1.9.1 branch, so that doesn't seem to be affected.
Test 421715-1.html happens to be the one after 458637-1.html. So maybe it's getting hammered by residual effects of 458637-1.html.
I tried running the test before and after the changes around 1a4e256b6894, and I got the same performance both times, so I can't see what might have changed there. I'll land my fix in bug 473680 to make 458637-1.html more reasonable, and then we'll see if that fixes the random orange.
My fix seems to have stopped these tests from failing. I guess we'll leave it at that.
I spoke too soon, there have been a lot of failures recently. Boris, you fixed 458637, any ideas spring to mind?
Not off the top of my head. :(