The reftest '413292-1.html' has been failing while loading on qm-xserve06 (Bug 432292) and qm-moz2mini01 (bug 432954). We're probably going to disable this test on mac in bug 432954, but this bug here is to investigate the underlying cause of the failure and fix the test. Failure log for qm-xserve06: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1210692843.1210695685.18911.gz Failure line: REFTEST UNEXPECTED FAIL (LOADING): file:///builds/slave/trunk_osx_6/mozilla/layout/reftests/bugs/413292-1.html
Note that the test has occasionally passed on qm-xserve06, at least twice that I know of. In particular: - The first cycle ever run on that system: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1210285576.1210288118.28002.gz - This cycle from today: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1210683414.1210686154.25362.gz
(In reply to comment #0) > The reftest '413292-1.html' has been failing while loading on qm-xserve06 > (Bug 432292) and qm-moz2mini01 (bug 432954). Oops, I mismatched the bug numbers with their machines. The correct pairing is: qm-moz2mini01 failure = bug 432292 qm-xserve06 failure = bug 432954
seems to run correctly on first pass after a clobber. Subsequent dep builds fail for some reason.
See also bug 465475, which is a slightly different sporadic failure to finish loading this test. Note that in that bug, we "timed out waiting for reftest-wait to be removed (after onload fired)", whereas on this bug here, we apparently never hit the onload at all.
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/ae6750d7e782 Re-enable reftest 413292-1.html on OS X.
This passes now https://treeherder.mozilla.org/#/jobs?repo=try&revision=df650250ae1559bee2807d40881f2a3329315c23 (The reason I noticed that is this test pointed out a problem in a patch I'm working on.)
Status: NEW → RESOLVED
Last Resolved: 11 months ago
status-firefox55: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in before you can comment on or make changes to this bug.