Closed Bug 688070 Opened 13 years ago Closed 13 years ago

multiple tests failing on stabilization branch

Categories

(Add-on SDK Graveyard :: General, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: myk, Unassigned)

Details

Some tests are failing on the stabilization branch:

error: TEST FAILED: test-content-proxy.testProxy (failure)
error: fail: functions are functions 2 ("[object Object]" doesn't match /\[object Function.*\]/)
info: Traceback (most recent call last):
  File "resource://testpkgs-api-utils-tests/test-content-proxy.js", line 227, in onDOMReady
    test.assertMatches(win.Object.prototype.toString.call(f), /\[object Function.*\]/, "functions are functions 2");
  File "resource://testpkgs-api-utils-lib/unit-test.js", line 139, in assertMatches
    this.fail(message);
  File "resource://testpkgs-api-utils-lib/unit-test.js", line 116, in fail
    console.trace();

And then a bunch of these:

error: An exception occurred.
Traceback (most recent call last):
  File "resource://testpkgs-api-utils-lib/tabs/tab.js", line 254, in null
    .getInterface(Ci.nsIWebNavigation)
Error: Permission denied for <moz-safe-about:blank> to create wrapper for object of class UnnamedClass
"]
error: TEST FAILED: test-page-mod.test tab worker on message (timed out)
console: [JavaScript Error: "TEST FAILED: test-page-mod.test tab worker on message (timed out)
"]

This looks awfully like problems we previously resolved.  Perhaps something went wrong with the merge, and some changes were accidentally reverted?  I could have sworn tests were passing after I merged last week, but perhaps I was mistaken.
Erm, my bad.  I was testing in a repository whose local stabilization branch hadn't yet had last week's master -> stabilization merge changeset merged into it.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.