Last Comment Bug 596237 - [SeaMonkey 2.1] TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/content/html/document/test/browser_bug592641.js
: [SeaMonkey 2.1] TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/cont...
Product: SeaMonkey
Classification: Client Software
Component: Testing Infrastructure (show other bugs)
: Trunk
: x86_64 Linux
-- normal (vote)
: seamonkey2.1b1
Assigned To:
Depends on: 592641
Blocks: SmTestFail
  Show dependency treegraph
Reported: 2010-09-14 08:43 PDT by Bruno 'Aqualon' Escherl
Modified: 2010-09-15 05:14 PDT (History)
4 users (show)
bugzillamozillaorg_serge_20140323: in‑testsuite+
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---

Remove event listeners (2.78 KB, patch)
2010-09-14 09:58 PDT,
bobbyholley: review+
Details | Diff | Splinter Review

Description User image Bruno 'Aqualon' Escherl 2010-09-14 08:43:29 PDT comm-central-trunk debug test mochitest-other&fulltext=1#err1

This fails after the test should be finished already. Perhaps similar issue to bug 595188?
Comment 1 User image 2010-09-14 09:04:14 PDT
Exactly the same problem... I hadn't noticed because I ran the tests locally on a debug build and the debug spew hid the unexpected fails, and because they happened after the test shutdown the harness claimed that the test passed :-(
Comment 2 User image 2010-09-14 09:58:18 PDT
Created attachment 475115 [details] [diff] [review]
Remove event listeners
Comment 3 User image Bobby Holley (:bholley) (busy with Stylo) 2010-09-14 11:09:07 PDT
Comment on attachment 475115 [details] [diff] [review]
Remove event listeners

Looks fine - r=bholley.

I'm curious why this is necessary though - those tabs are removed, so their listeners should go away, no?
Comment 4 User image 2010-09-14 11:14:46 PDT
(In reply to comment #3)
> I'm curious why this is necessary though - those tabs are removed, so their
> listeners should go away, no?
Unfortunately SeaMonkey's undo close tab keeps the browser around so while you can undo an accidental close tab very quickly a quirk is that it loads about:blank in the browser too, thus causing unexpected extra load events.
Comment 6 User image Bruno 'Aqualon' Escherl 2010-09-15 03:52:22 PDT
Don't see this failure anymore on our tinderboxes.


Note You need to log in before you can comment on or make changes to this bug.