Closed Bug 595188 Opened 14 years ago Closed 14 years ago

[SeaMonkey 2.1, mochitest-browser-chrome] TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/toolkit/content/tests/browser/browser_bug594509.js | about:rights content loaded

Categories

(Toolkit Graveyard :: XULRunner, defect)

defect
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED
mozilla2.0b7

People

(Reporter: bugzilla, Assigned: Callek)

References

(Blocks 1 open bug)

Details

Attachments

(2 files, 1 obsolete file)

Attached file log of testrun
This failure is quite strange. The test runs fine alone, but fails if I run all tests from toolkit/content/tests/browser/ The strang thing is, I first get this output: TEST-PASS | chrome://mochikit/content/browser/toolkit/content/tests/browser/browser_bug594509.js | about:rights loaded Document about:rights loaded successfully TEST-PASS | chrome://mochikit/content/browser/toolkit/content/tests/browser/browser_bug594509.js | about:rights content loaded TEST-INFO | chrome://mochikit/content/browser/toolkit/content/tests/browser/browser_bug594509.js | Test took 0.351s to complete After that comes the next test: TEST-START | chrome://mochikit/content/browser/toolkit/content/tests/browser/browser_save_resend_postdata.js And directly after that I get the test failure: TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/toolkit/content/tests/browser/browser_bug594509.js | about:rights content loaded JavaScript error: , line 0: uncaught exception: 2147942487 I've attached the whole testrun log, if I've overlooked something.
This is a new test, added by bug 594509: http://hg.mozilla.org/mozilla-central/rev/c966fbc9ffd4 Just guessing, but it looks like maybe gBrowser.removeTab(tab); is not processed before the next test starts, and that executeSoon(finish); might help !?
Blocks: 594509
Severity: normal → major
Component: Testing Infrastructure → XULRunner
Product: SeaMonkey → Toolkit
QA Contact: testing-infrastructure → xulrunner
Hardware: x86_64 → All
(In reply to comment #1) > This is a new test, added by bug 594509: > http://hg.mozilla.org/mozilla-central/rev/c966fbc9ffd4 > > Just guessing, but ... Good guess but wrong. The problem is that this test RUNS and PASSES just fine... TEST-START | chrome://mochikit/content/browser/toolkit/content/tests/browser/browser_bug594509.js TEST-PASS | chrome://mochikit/content/browser/toolkit/content/tests/browser/browser_bug594509.js | about:rights loaded TEST-PASS | chrome://mochikit/content/browser/toolkit/content/tests/browser/browser_bug594509.js | about:rights content loaded TEST-INFO | chrome://mochikit/content/browser/toolkit/content/tests/browser/browser_bug594509.js | Test took 0.351s to complete THEN TEST-PASS | chrome://mochikit/content/browser/toolkit/content/tests/browser/browser_bug594509.js | about:rights loaded TEST-START | chrome://mochikit/content/browser/toolkit/content/tests/browser/browser_save_resend_postdata.js TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/toolkit/content/tests/browser/browser_bug594509.js | about:rights content loaded The reason is that the 594509 test does not _unregister_ its load listener. CC-ing author, the person who pushed and reviewer of this.
Attached patch Fix it (obsolete) — Splinter Review
This properly removes the event listener. I'm still unsure on why this doesn't fail on Firefox.
Assignee: nobody → bugspam.Callek
Status: NEW → ASSIGNED
Attachment #474318 - Flags: review?(gavin.sharp)
better fix
Attachment #474318 - Attachment is obsolete: true
Attachment #474319 - Flags: review?(gavin.sharp)
Attachment #474318 - Flags: review?(gavin.sharp)
(In reply to comment #2) > Good guess but wrong. > The problem is that this test RUNS and PASSES just fine... > The reason is that the 594509 test does not _unregister_ its load listener. Yes, that is exactly what I meant: I just assumed actually removing the tab does/would remove its listener too. But maybe was I wrong at that?
Attachment #474319 - Flags: review?(gavin.sharp)
Attachment #474319 - Flags: review+
Attachment #474319 - Flags: approval2.0+
(In reply to comment #5) > I just assumed actually removing the tab does/would remove its listener too. > But maybe was I wrong at that? No, that's right. But SeaMonkey's removeTab apparently triggers a synchronous about:blank load...
(In reply to comment #6) > But SeaMonkey's removeTab apparently triggers a synchronous > about:blank load... (Ah, I had forgotten about that ;->)
Keywords: checkin-needed
Attachment #474319 - Attachment description: better fix. → better fix. [Checked in: Comment 8]
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0b7
V.Fixed, per http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1284815013.1284818289.1169.gz OS X 10.5 comm-central-trunk debug test mochitest-other on 2010/09/18 06:03:33
Status: RESOLVED → VERIFIED
Flags: in-testsuite+
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: