Benoit: did you mean this to be linked to the randomorange bug? If it's not random orange we should figure out who caused it and back it out. It seems pretty consistent this afternoon, actually, not so random.
This timeout is happening a lot today, starting with this push:http://hg.mozilla.org/mozilla-central/rev/b71c8de1a91dSeems to be happening consistently, so probably not a random orange.No idea what this is about.
Reposting because bugzilla killed my formatting: This timeout is happening a lot today, starting with this push: http://hg.mozilla.org/mozilla-central/rev/b71c8de1a91d Seems to be happening consistently, so probably not a random orange. No idea what this is about.
No idea why i assigned to Graphics. Unsetting. Please help assign to the right component, given that it's probably caused by http://hg.mozilla.org/mozilla-central/rev/b71c8de1a91d or http://hg.mozilla.org/mozilla-central/rev/58e7b99bb1d0
Component: Graphics → General
QA Contact: thebes → general
Ah, everytime this test fails, 424631-1.html is also failing. I guess this should be treated as one bug.
Summary: /reftest/tests/layout/reftests/bugs/424465-1.html | timed out waiting for reftest-wait to be removed (after onload fired) → /reftest/tests/layout/reftests/bugs/424465-1.html | timed out waiting for reftest-wait to be removed (after onload fired) ; also 424631-1.html failing
Josh: can you have a look at these failures, they seem to date back to your push.
Possibly fixed by http://hg.mozilla.org/mozilla-central/rev/4eca390568b4
We checked in a patch that caused a failure and then backed it out. The backout looks good to me. Maybe try clobbering? Aside from that I don't know how we could have caused this problem.
Haven't seen this since the backout. -> FIXED.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.