Closed Bug 753121 Opened 12 years ago Closed 12 years ago

failing test-content-worker.test:sample

Categories

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

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 751069

People

(Reporter: irakli, Unassigned)

Details

Tinderbox is orange for Aurora because of:

error: TEST FAILED: test-content-worker.test:sample (timed out)

Also it looks like it because of thrown exception:

error: An exception occurred.
Traceback (most recent call last):
  File "}", line 1, in }:
  File "    self.on("message", function (data) {if (data == "hi!") {self.postMessage("bye!");}})", line NaN, in     self.on
  File "    var myLocation = window.location.toString()", line NaN, in     var myLocation = window.location.toString
  File "javascript", line NaN, in 
  File "}", line 2, in }:
  File "    self.on("message", function (data) {if (data == "hi!") {self.postMessage("bye!");}})", line NaN, in     self.on
  File "    var myLocation = window.location.toString()", line NaN, in     var myLocation = window.location.toString
  File "javascript", line NaN, in WorkerScope
TypeError: window.location is undefined
The fix for this (bug 751077) landed in Nightly and has yet to be uplifted to Aurora.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
It looks like using document.location instead of window.location here:
https://github.com/mozilla/addon-sdk/blob/master/packages/api-utils/tests/test-content-worker.js#L53

Solves the failure on Aurora, but I'm not sure what are the consequences of such change are. I find it little awkward that document.location is there while window.location is not and I think it maybe related to Bug 695480. Also this issue no longer appears on Nightly which suggests that maybe there was some regression that made it to Aurora but is already fixed in Nightly.

I'm CC-ing Alex to see if he has a better idea since he tracked down most of the issues "can't access dead object" exceptions which I suspect are related to this.
You need to log in before you can comment on or make changes to this bug.