Closed
Bug 439164
Opened 16 years ago
Closed 15 years ago
[FIXr]intermittent mochitest failure in test_bug413310
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: joduinn, Assigned: bzbarsky)
References
Details
(Keywords: fixed1.9.0.2, intermittent-failure)
Attachments
(1 file)
2.18 KB,
patch
|
joduinn
:
review+
|
Details | Diff | Splinter Review |
We're investigating intermittent test failures, and find that this test sometimes passes, sometimes fails, even when there are no code changes. Its happened with a few builds this week. (It was happening before, as well as after, the recent NetApp woes). Can you review how this test was written and see if the test can be made more robust? suite: mochitest stdio line#13065 error msg: *** 13678 ERROR FAIL Error thrown during test: doNextStep is not defined /tests/docshell/test/test_bug413310.html Note: This test does not *break* builds, they only fail out as orange.
![]() |
Assignee | |
Comment 1•16 years ago
|
||
Hmm. Yeah, I think I see how this could happen. Diff that should help coming up.
![]() |
Assignee | |
Comment 2•16 years ago
|
||
The comments more or less explain what the change is here.
Attachment #325131 -
Flags: review?(joduinn)
Comment 3•16 years ago
|
||
John - is the patch good to go?
Comment 4•15 years ago
|
||
Boris: this should probably be reviewed by Waldo (who's afk), sayrer or myself. R+ from me though you should add a space to the comment line (NOTget): +// modified accordingly! It assumes that subframes do NOTget bfcached. I'm not sure this will fix the problem as we're still using explicit timeout values here, but the order might improve reliability. Also, as a final note, it's well-past May now. Might want to change your "very little time" message. Helpful tip provided at no extra charge!
Reporter | ||
Updated•15 years ago
|
Attachment #325131 -
Flags: review?(joduinn) → review+
Reporter | ||
Comment 5•15 years ago
|
||
Minor nit: can you fix typo in comment "do NOTget " should be "do NOT get "!
![]() |
Assignee | |
Comment 6•15 years ago
|
||
> I'm not sure this will fix the problem as we're still using explicit timeout
> values here
That's OK. All that's needed there is that the code run async. When is not important. I almost changed the timeout value to 0 to make that clearer.
And fixed the name. If forgot to update it when late May didn't free up...
I won't be able to check this in for probably a week or so. If someone can get to it before then, great.
Assignee: nobody → bzbarsky
Keywords: checkin-needed
Summary: intermittent mochitest failure in test_bug413310 → [FIXr]intermittent mochitest failure in test_bug413310
Updated•15 years ago
|
Version: unspecified → Trunk
Comment 7•15 years ago
|
||
Gavin or reed can you land this?
Comment 8•15 years ago
|
||
Landed on mozilla-central: http://hg.mozilla.org/mozilla-central/index.cgi/rev/6f6c7d842726 and CVS trunk: mozilla/docshell/test/test_bug413310.html 1.2
Keywords: checkin-needed
![]() |
Assignee | |
Comment 9•15 years ago
|
||
Should be fixed.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•15 years ago
|
Keywords: fixed1.9.0.2
Updated•15 years ago
|
Whiteboard: [orange]
Updated•11 years ago
|
Keywords: intermittent-failure
Updated•11 years ago
|
Whiteboard: [orange]
You need to log in
before you can comment on or make changes to this bug.
Description
•