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)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
1.2
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.
Reporter | ||
Updated•13 years ago
|
Priority: -- → P1
Target Milestone: --- → 1.1
Updated•13 years ago
|
Assignee: nobody → rFobic
Assignee | ||
Comment 1•13 years ago
|
||
Pointer to Github pull-request
Assignee | ||
Updated•13 years ago
|
Attachment #551411 -
Flags: review?(myk)
Reporter | ||
Comment 2•13 years ago
|
||
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+
Reporter | ||
Comment 3•13 years ago
|
||
https://github.com/mozilla/addon-sdk/commit/192eab036f3a75e7af01f4f534d7fea2a317ae9b
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•13 years ago
|
||
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.
Description
•