Closed Bug 468189 Opened 17 years ago Closed 17 years ago

test_bug364461.xul sporadic failures | Did not receive all expected events

Categories

(Core :: DOM: Navigation, defect)

defect
Not set
trivial

Tracking

()

RESOLVED FIXED
mozilla1.9.2a1

People

(Reporter: robert.strong.bugs, Assigned: bzbarsky)

Details

(Keywords: fixed1.9.1, Whiteboard: [fixed1.9.1b99])

ccing test author.
Given that when it does fail, it doesn't fail consistently at the same place, is it not the code at http://mxr.mozilla.org/mozilla-central/source/docshell/test/chrome/bug364461_window.xul#82 which is to blame? The test will fail if it doesn't complete within 5000ms of being loaded.
right, that could happen if the test is running very slowly. Possible solutions: 1. raise the timeout 2. drop the timeout so that the mochitest timeout should itself be triggered in case of failure (which should be 300 seconds http://mxr.mozilla.org/mozilla-central/source/testing/mochitest/tests/SimpleTest/TestRunner.js#15). 2. seems to be the cleaner option.
Er, yes. It should just depend on the main mochitest timeout, not set up its own timeout thing. I pushed http://hg.mozilla.org/mozilla-central/rev/53f438686fa2 to remove that timeout stuff. This should be fixed.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
This test failed on a 1.9.1 tinderbox today: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox3.1/1235679961.1235685558.26203.gz *** 161 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/chrome/docshell/test/chrome/test_bug364461.xul | Did not receive all expected events bz, would it make sense to land your fix from comment 4 on the 1.9.1 branch?
Probably, yeah. Let's do it.
This never made it to 1.9.1...
Flags: wanted1.9.1+
Keywords: checkin-needed
Assignee: nobody → bzbarsky
Flags: in-testsuite+
Whiteboard: [needs 1.9.1 landing]
Target Milestone: --- → mozilla1.9.2a1
Severity: normal → trivial
Whiteboard: [needs 1.9.1 landing] → [fixed1.9.1rc1]
Whiteboard: [fixed1.9.1rc1] → [fixed1.9.1b99]
You need to log in before you can comment on or make changes to this bug.