test-windows.testOnOpenOnCloseListeners test failures on Windows

RESOLVED FIXED

Status

Add-on SDK
General
RESOLVED FIXED
8 years ago
7 years ago

People

(Reporter: myk, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
On Windows 7, with both Firefox 3.6 and trunk nightlies, the Windows API tests frequently fail with errors like the following:

error: TEST FAILED: test-windows.testOnOpenOnCloseListeners (timed out)
error: fail: Event received twice
info: Traceback (most recent call last):
  File "resource://jetpack-core-jetpack-core-lib/errors.js", line 49, in anonymous
    return callback.apply(this, arguments);
  File "resource://jetpack-core-jetpack-core-lib/window-utils.js", line 105, in handleEvent
    this._regWindow(window);
  File "resource://jetpack-core-jetpack-core-lib/window-utils.js", line 83, in _regWindow
    this.delegate.onTrack(window);
  File "resource://jetpack-core-jetpack-core-lib/windows.js", line 241, in anonymous
    })(safeWindowObj);
  File "resource://jetpack-core-jetpack-core-lib/errors.js", line 49, in anonymous
    return callback.apply(this, arguments);
  File "resource://jetpack-core-jetpack-core-lib/windows.js", line 240, in anonymous
    callback.call(exports.browserWindows, safeWindowObj);
  File "resource://jetpack-core-jetpack-core-tests/test-windows.js", line 76, in listener1
    test.fail("Event received twice");
  File "resource://jetpack-core-jetpack-core-lib/unit-test.js", line 145, in fail
    console.trace();
(Reporter)

Comment 1

8 years ago
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product.

To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
(Reporter)

Comment 2

7 years ago
I don't see this anymore.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.