Closed Bug 640519 Opened 14 years ago Closed 12 years ago

[SeaMonkey (and Firefox)] mochitest-browser-chrome: .../browser/browser_bug562797.js and .../browser/browser_discovery.js fail since 2011.02.28

Categories

(Toolkit :: Add-ons Manager, defect)

Product:
Toolkit
Component:
Add-ons Manager
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
blocking2.0 --- -
status2.0 --- ?

People

(Reporter: sgautherie, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: regression, Whiteboard: [perma-orange])

Ftr, there used to be bug 608586, which was fixed. Regression timeframe: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=459f9ea753a2&tochange=ec8a059bea58 (10 changesets) Bug 635844 has been ported in bug 640035. Yet I'm guessing there is something "wrong" with http://hg.mozilla.org/mozilla-central/rev/a7b9ace8b3a3 This is happening on Windows. I can't tell about Linux and MacOSX ftb. *** http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1298991327.1298995246.11338.gz WINNT 5.2 comm-central-trunk debug test mochitest-other on 2011/03/01 06:55:27 { TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_bug562797.js | Browser should be visible - Got [object XULElement @ 0x5dcf5d8 (native @ 0xbaa6bd8)], expected [object XULElement @ 0xba87ee0 (native @ 0xb72ef08)] TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_bug562797.js | Should have loaded the right url - Got https://example.com/browser/toolkit/mozapps/extensions/test/browser/discovery.html, expected https://example.com/browser/toolkit/mozapps/extensions/test/browser/releaseNotes.xhtml TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_bug562797.js | canGoBack should be correct - Got false, expected true TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_bug562797.js | Test timed out TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_bug562797.js | Found a tab after previous test timed out: about:addons TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_discovery.js | Should have loaded the right url - Got null, expected https://example.com/browser/toolkit/mozapps/extensions/test/browser/discovery.html TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_discovery.js | Should have loaded the right url - Got null, expected https://example.com/browser/toolkit/mozapps/extensions/test/browser/discovery.html TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_discovery.js | Should have shown the error page TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_discovery.js | Should start loading again TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_discovery.js | Should have loaded the right url - Got null, expected https://example.com/browser/toolkit/mozapps/extensions/test/browser/discovery.html TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_discovery.js | Should have shown the error page TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_discovery.js | Should start loading again TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_discovery.js | Should have loaded the right url - Got null, expected https://example.com/browser/toolkit/mozapps/extensions/test/browser/discovery.html TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_discovery.js | Should have shown the error page TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_discovery.js | Should start loading again TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_discovery.js | Should have loaded the right url - Got null, expected https://example.com/browser/toolkit/mozapps/extensions/test/browser/discovery.html TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_discovery.js | Should have loaded the right url - Got https://example.com/browser/toolkit/mozapps/extensions/test/browser/discovery.html, expected https://example.com/browser/toolkit/mozapps/extensions/test/browser/releaseNotes.xhtml TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_discovery.js | Should have loaded the right url - Got https://example.com/browser/toolkit/mozapps/extensions/test/browser/discovery.html, expected https://example.com/browser/toolkit/mozapps/extensions/test/browser/releaseNotes.xhtml TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_discovery.js | Should have loaded the right url - Got null, expected https://example.com/browser/toolkit/mozapps/extensions/test/browser/discovery.html TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_discovery.js | Should have loaded the right url - Got null, expected http://example.com/browser/toolkit/mozapps/extensions/test/browser/discovery.html TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_discovery.js | Should have loaded the right url - Got http://example.com/browser/toolkit/mozapps/extensions/test/browser/discovery.html, expected https://example.com/browser/toolkit/mozapps/extensions/test/browser/discovery.html } There is also "JavaScript error: chrome://mochikit/content/tests/SimpleTest/EventUtils.js, line 60: aTarget is null" which reminds me of bug 604129, fwiw. When I execute browser_bug562797.js alone on my local Windows 2000, I get, in addition, multiple "Error: Ci is not defined Source File: chrome://mozapps/content/extensions/extensions.js Line: 1794" which is odd as it's defined as a const in that very file :-<
(In reply to comment #0) > TEST-UNEXPECTED-FAIL | > chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_bug562797.js > | Browser should be visible - Got [object XULElement @ 0x5dcf5d8 (native @ > 0xbaa6bd8)], expected [object XULElement @ 0xba87ee0 (native @ 0xb72ef08)] Fwiw, I tried adding ".id" and got "... - Got discover-loading, expected discover-browser".
Very doubtful I'll have time to look at this anytime soon
(In reply to comment #0) > When I execute browser_bug562797.js alone on my local Windows 2000, I get, in > addition, multiple > "Error: Ci is not defined > Source File: chrome://mozapps/content/extensions/extensions.js > Line: 1794" > which is odd as it's defined as a const in that very file :-< If I s/Ci./Components.interfaces./g in that file, I then get { Error: Components is not defined Source File: chrome://mozapps/content/extensions/extensions.js Line: 1794 } Very odd indeed! (It makes me think about spidermonkey regressions SeaMonkey triggered in the (recent) past :-|)
Fwiw, .../browser-window/*.js are passing. *** Fwiw, here are some more logs: { TEST-INFO | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_bug562797.js | Running test 1 ... xpi: Loading bootstrap scope from c:\docume~1\seabld\locals~1\temp\tmpke8mqb\extensions\addon2@tests.mozilla.org.xpi *** WARN addons.xpi: Error loading bootstrap.js for addon2@tests.mozilla.org: Error opening input stream (invalid filename?) *** WARN addons.xpi: Add-on addon2@tests.mozilla.org is missing bootstrap method uninstall *** LOG addons.xpi: Loading bootstrap scope from c:\docume~1\seabld\locals~1\temp\tmpke8mqb\extensions\addon3@tests.mozilla.org.xpi *** WARN addons.xpi: Error loading bootstrap.js for addon3@tests.mozilla.org: Error opening input stream (invalid filename?) *** WARN addons.xpi: Add-on addon3@tests.mozilla.org is missing bootstrap method uninstall *** WARN addons.xpi: Add-on addon4@tests.mozilla.org is missing bootstrap method shutdown *** WARN addons.xpi: Add-on addon4@tests.mozilla.org is missing bootstrap method uninstall *** WARN addons.xpi: Add-on addon5@tests.mozilla.org is missing bootstrap method shutdown *** WARN addons.xpi: Add-on addon5@tests.mozilla.org is missing bootstrap method uninstall *** WARN addons.xpi: Add-on addon6@tests.mozilla.org is missing bootstrap method shutdown *** WARN addons.xpi: Add-on addon6@tests.mozilla.org is missing bootstrap method uninstall *** LOG addons.xpi: Cancelling download of http://example.com/browser/toolkit/mozapps/extensions/test/browser/browser_bug557956_7_2.xpi *** LOG addons.xpi: Cancelling download of http://example.com/browser/toolkit/mozapps/extensions/test/browser/browser_bug557956_8_2.xpi *** LOG addons.xpi: Cancelling download of http://example.com/browser/toolkit/mozapps/extensions/test/browser/browser_bug557956_9_2.xpi *** LOG addons.xpi: Cancelling download of http://example.com/browser/toolkit/mozapps/extensions/test/browser/browser_bug557956_7_2.xpi *** LOG addons.xpi: Cancelling download of http://example.com/browser/toolkit/mozapps/extensions/test/browser/browser_bug557956_8_2.xpi *** LOG addons.xpi: Cancelling download of http://example.com/browser/toolkit/mozapps/extensions/test/browser/browser_bug557956_9_2.xpi ... TEST-PASS | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_bug562797.js | Should have an add-ons manager window TEST-INFO | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_bug562797.js | Running test 2 TEST-INFO | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_bug562797.js | Part 1 ... ###!!! ASSERTION: XPConnect is being called on a scope without a 'Components' property! (stack and details follow): 'Error', file e:/builds/slave/comm-cen-trunk-w32-dbg/build/mozilla/js/src/xpconnect/src/xpcwrappednativescope.cpp, line 761 The current JS stack is: JavaScript stack is empty And the object whose scope lacks a 'Components' property is: xul!xpc_LocalizeContext+0x0000000000010B60 xul!mozilla::layers::LayerManagerOGL::operator=+0x0000000000805862 xul!xpc_LocalizeContext+0x00000000000DEA74 ... WARNING: Not same origin error!: file e:/builds/slave/comm-cen-trunk-w32-dbg/build/mozilla/dom/base/nsJSEnvironment.cpp, line 324 JavaScript error: chrome://mozapps/content/extensions/extensions.js, line 1794: Ci is not defined ... TEST-INFO | chrome://mochitests/content/browser/toolkit/mozapps/extensions/test/browser/browser_bug562797.js | Part 2 }
Keywords: assertion
Summary: [SeaMonkey] mochitest-browser-chrome: browser_bug562797.js and browser_discovery.js fail since 2011.02.28. → [SeaMonkey] mochitest-browser-chrome: .../browser/browser_bug562797.js and .../browser/browser_discovery.js fail since 2011.02.28.
Firefox has (same or different) js warnings and assertions too.!.
Summary: [SeaMonkey] mochitest-browser-chrome: .../browser/browser_bug562797.js and .../browser/browser_discovery.js fail since 2011.02.28. → [SeaMonkey (and Firefox)] mochitest-browser-chrome: .../browser/browser_bug562797.js and .../browser/browser_discovery.js fail since 2011.02.28. (ASSERTION too...)
"blocking2.0=?": There are really odd things going on here (on Firefox): undefined Ci, assertions, ..., that should at least be investigated asap.
blocking2.0: --- → ?
OSX 10.6 SeaMonkey report this bug too.
OS: Windows Server 2003 → All
The undefined Components/Ci is a known issue where we close the add-ons manager before the get add-ons page has completed loading. We need to remove the progress listener on close to avoid us getting called after the window is gone away.
blocking2.0: ? → -
(In reply to comment #8) > The undefined Components/Ci is a known issue Ah. Is a bug filed? *** Related or not, the assertion part is bug 614359.
Depends on: 614359
Keywords: assertion
Summary: [SeaMonkey (and Firefox)] mochitest-browser-chrome: .../browser/browser_bug562797.js and .../browser/browser_discovery.js fail since 2011.02.28. (ASSERTION too...) → [SeaMonkey (and Firefox)] mochitest-browser-chrome: .../browser/browser_bug562797.js and .../browser/browser_discovery.js fail since 2011.02.28
(In reply to comment #9) > (In reply to comment #8) > > The undefined Components/Ci is a known issue > > Ah. Is a bug filed? Could have sworn it was but I'm not finding it right now
(In reply to comment #10) > (In reply to comment #9) > > (In reply to comment #8) > > > The undefined Components/Ci is a known issue > > > > Ah. Is a bug filed? > > Could have sworn it was but I'm not finding it right now So, into gDiscoverView, something like: shutdown: function() { var self = this; self._browser.removeProgressListener(self); }, ? This just fixes the Ci issue, doesn't resolve the problem this bug is about though.
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1303441548.1303445522.14025.gz WINNT 5.2 comm-central-trunk debug test mochitest-other on 2011/04/21 20:05:48 http://hg.mozilla.org/mozilla-central/rev/357593f3abbd http://hg.mozilla.org/comm-central/rev/0801160b7f27 still had this bug. http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1303489658.1303494388.6628.gz WINNT 5.2 comm-central-trunk debug test mochitest-other on 2011/04/22 09:27:38 http://hg.mozilla.org/mozilla-central/rev/e00435bb54b5 http://hg.mozilla.org/comm-central/rev/1cb31f2bbbfc Bug disappeared on mozilla6. (But still there on mozilla2.) Fix timeframes: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=357593f3abbd&tochange=e00435bb54b5 12 changesets http://hg.mozilla.org/comm-central/pushloghtml?fromchange=0801160b7f27&tochange=1cb31f2bbbfc 4 changesets Let's keep this bug open until SM 2.1 is fixed, or at least we have pinpointed what Trunk fix was.
Hasn't happened in 9 months. -->WFM
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.