Closed Bug 676715 Opened 13 years ago Closed 13 years ago

test-private-browsing.testActivateDeactivate and .testStart time out

Categories

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

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: myk, Assigned: irakli)

References

Details

Attachments

(1 file)

Two private-browsing tests started failing on all platforms after this recent merge from fx-team to central <http://tbpl.mozilla.org/?tree=Firefox&noignore=1&rev=0fbdefb0a9b5>:

info: executing 'test-private-browsing.testActivateDeactivate'
error: TEST FAILED: test-private-browsing.testActivateDeactivate (timed out)
console: [JavaScript Error: "TEST FAILED: test-private-browsing.testActivateDeactivate (timed out)
"]
info: executing 'test-private-browsing.testStart'
error: TEST FAILED: test-private-browsing.testStart (timed out)
console: [JavaScript Error: "TEST FAILED: test-private-browsing.testStart (timed out)
"]

http://hg.mozilla.org/mozilla-central/rev/1a9f0823fdba from bug 651643 is the obvious "changeset of interest" in this case.  This could be a regression from that change, but it seems more likely that we need to update the SDK tests to take the underlying change in behavior into account.
Blocks: 629263
Priority: -- → P1
Target Milestone: --- → 1.1
Assignee: nobody → rFobic
Attachment #551411 - Flags: review?(myk)
Comment on attachment 551411 [details]
Pointer to Github pull request: https://github.com/mozilla/addon-sdk/pull/223

Looks good, works, r=myk.
Attachment #551411 - Flags: review?(myk) → review+
https://github.com/mozilla/addon-sdk/commit/192eab036f3a75e7af01f4f534d7fea2a317ae9b
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
This doesn't actually happen on the Firefox branch that SDK 1.1 is targeting (currently, the beta branch), so we don't need to fix this for 1.1.
Target Milestone: 1.1 → 1.2
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: