Closed
Bug 994213
Opened 10 years ago
Closed 10 years ago
Intermittent test-page-worker:testRedirect timeouts
Categories
(Add-on SDK Graveyard :: General, defect)
Tracking
(firefox29 unaffected, firefox30 unaffected, firefox31 fixed, firefox-esr24 unaffected)
RESOLVED
FIXED
mozilla31
Tracking | Status | |
---|---|---|
firefox29 | --- | unaffected |
firefox30 | --- | unaffected |
firefox31 | --- | fixed |
firefox-esr24 | --- | unaffected |
People
(Reporter: jsantell, Assigned: evold)
Details
(Keywords: intermittent-failure)
Attachments
(1 file)
Nestled in an intermittent (Bug 942111), looks like this page-worker test is timing out (happened a few times in 942111) TEST-UNEXPECTED-FAIL | tests/test-page-worker.testRedirect | Test output exceeded timeout (300s). https://tbpl.mozilla.org/php/getParsedLog.php?id=37509977&tree=Mozilla-Inbound#error1
Updated•10 years ago
|
Keywords: intermittent-failure
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → evold
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8407283 -
Flags: review?(jsantell)
Reporter | ||
Updated•10 years ago
|
Attachment #8407283 -
Flags: review?(jsantell) → review+
Comment 2•10 years ago
|
||
Commits pushed to master at https://github.com/mozilla/addon-sdk https://github.com/mozilla/addon-sdk/commit/8670b1d1b291586981ca515d82c083a7887e6f68 Bug 994213 - Intermittent test-page-worker:testRedirect timeouts https://github.com/mozilla/addon-sdk/commit/3f001c68ac1b6274950fe0d2b868fded453fcf8d Merge pull request #1463 from erikvold/994213 Bug 994213 - Intermittent test-page-worker:testRedirect timeouts r=jsantell
Is this fixed?
Flags: needinfo?(evold)
Assignee | ||
Comment 4•10 years ago
|
||
We can reopen if it is not resolved.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(evold)
Resolution: --- → FIXED
Updated•10 years ago
|
status-firefox29:
--- → unaffected
status-firefox30:
--- → unaffected
status-firefox31:
--- → fixed
status-firefox-esr24:
--- → unaffected
Target Milestone: --- → mozilla31
Comment 5•10 years ago
|
||
Hi, I got the same issue in mozilla 33.1 version.
You need to log in
before you can comment on or make changes to this bug.
Description
•