intermittent failure test-windows.testActiveWindow: nonBrowserWindow is null

RESOLVED FIXED

Status

Add-on SDK
General
P1
normal
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: ochameau, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
http://tinderbox.mozilla.org/showlog.cgi?log=Jetpack/1320375417.1320375713.22445.gz
and
http://tinderbox.mozilla.org/showlog.cgi?log=Jetpack/1320350755.1320351052.5866.gz
Both linux64, but I don't think it to be limited to these OS.


info: executing 'test-windows.testActiveWindow'
info: pass: Correct number of browser windows
info: pass: Correct number of windows returned by iterator
console: [JavaScript Warning: "reference to undefined property this._value" {file: "chrome://browser/content/urlbarBindings.xml" line: 644}]
NEXT ERROR console: [JavaScript Error: "nonBrowserWindow is null" {file: "resource://d96529e1-0589-448d-af84-17d622c38ca3-at-jetpack-api-utils-lib/cuddlefish.js -> resource://d96529e1-0589-448d-af84-17d622c38ca3-at-jetpack-addon-kit-tests/test-windows.js" line: 231}]
error: TEST FAILED: test-windows.testActiveWindow (timed out)
info: executing 'test-windows.testAutomaticDestroy'
info: pass: Unloaded windows instance is destroyed and inactive
info: executing 'test-windows.testOnOpenOnCloseListeners'
error: TEST FAILED: test-windows.testOnOpenOnCloseListeners (failure)


It may be related to some issue I'm facing while fixing bug 699450.
As we later get this exception:
Traceback (most recent call last):
  File "resource://272b9222-d62d-4644-8baa-9d30a4d0a6fa-at-jetpack-api-utils-lib/tabs/tab.js", line 93, in destroy
    this._browser.removeEventListener(EVENTS.ready.dom, this._onReady,
NEXT ERROR TypeError: this._browser is null
(Reporter)

Updated

6 years ago
Blocks: 629263

Updated

6 years ago
Priority: -- → P1
Summary: intermitent failure test-windows.testActiveWindow: nonBrowserWindow is null → intermittent failure test-windows.testActiveWindow: nonBrowserWindow is null
(Reporter)

Comment 1

6 years ago
Looks like another automagically fixed.
Again, please reopen it if you see it!
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.