Closed Bug 454513 Opened 16 years ago Closed 16 years ago

browser_bug453896.js fails on all SeaMonkey unit test boxes

Categories

(Core :: Layout, defect)

defect
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla1.9.1b1

People

(Reporter: sgautherie, Assigned: kairo)

References

Details

Attachments

(1 file)

Since that (bug) test landed, it fails for SeaMonkey on all 3 platforms: [ http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1220968348.1220974177.20273.gz Linux comm-central dep unit test on 2008/09/09 06:52:28 http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1220971042.1220976375.25536.gz MacOSX 10.4 comm-central dep unit test on 2008/09/09 07:37:22 http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1220969059.1220973180.17477.gz Win2k3 comm-central dep unit test on 2008/09/09 07:04:19 ]
Flags: blocking1.9.1?
Blocks: 454524
The bug mentioned above is bug 453896 and the failure line is: TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/layout/style/test/browser_bug453896.js | Timed out Now that we have this noted in comments, adjusting summary to be more easily parseable by a human :)
Summary: [SeaMonkey] "TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/layout/style/test/browser_bug453896.js | Timed out" → browser_bug453896.js fails on all SeaMonkey unit test boxes
Hmmm. I thought the directory I was exporting it to was for Firefox browser tests. I'm surprised that SeaMonkey is using the same directory. I don't know if it's easy to make the test work in both. If not, probably the right thing to do is ifdef the makefile.
The directory is actually for "tests running with browser chrome" and as SeaMonkey also has browser chrome, we're running all we can run from that suite as well. Making that test |ifdef MOZ_PHOENIX| is probably the right thing to do if it tests Firefox specifics even though it lives in Gecko code.
For what it's worth, all it really tests is "run the following mochitests in a Web page that's been opened in a new tab and *not* switched to".
It looks like the test itself actually runs well, it's some other test before it that causes us to fail on this one.
Actually, what I see here is two event listeners that are added but never removed, in http://mxr.mozilla.org/mozilla-central/source/docshell/test/browser/browser_bug441169.js#16 and http://mxr.mozilla.org/mozilla-central/source/layout/style/test/browser_bug453896.js#16 - when I remove the test of the former from the suite, the latter succeeds.
Yeah, probably both listeners ought to be removed. The first is worse since it's on Window rather than the tab (which is only used once).
This patch removes the listeners and makes the tests succeed. I actually guess that the listener in the new test isn't the problem as it's browser goes away with the tab, but it's cleaner to remove the listener anyway. The one the window is surely something we must remove, I don't know why Firefox doesn't run into a failure somewhere with that.
Assignee: nobody → kairo
Attachment #337992 - Flags: review?(dbaron)
Comment on attachment 337992 [details] [diff] [review] remove listeners in the right places [Checkin: Comment 10] r=dbaron, although you might also want to run it by whoever maintains the browser test harness (which I probably should have done the first time, too...) (though if whoever that is isn't responsive, it's probably ok just to land it...)
Attachment #337992 - Flags: review?(dbaron) → review+
not sure who owns the browser harness, but I figured when the other tests in http://mxr.mozilla.org/mozilla-central/source/docshell/test/browser (at least those SeaMonkey builds) are removing their listeners, it should be the correct thing to do - esp. when it fixes the tests locally here. Pushed as http://hg.mozilla.org/mozilla-central/rev/c9482d51ef47 - marking FIXED on the assumption that unit test boxes see the same success as my local machine, please reopen if that's not happening.
Status: NEW → RESOLVED
Closed: 16 years ago
Flags: blocking1.9.1?
Resolution: --- → FIXED
Comment on attachment 337992 [details] [diff] [review] remove listeners in the right places [Checkin: Comment 10] Yeah, this is fine. Tests are supposed to clean up after themselves as much as they can. (Though I do wonder why these were causing test failures only in SeaMonkey...)
Blocks: 454717
Attachment #337992 - Attachment description: remove listeners in the right places → remove listeners in the right places [Checkin: Comment 10]
No longer blocks: 454524
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: