Closed Bug 846854 Opened 12 years ago Closed 12 years ago

TEST-UNEXPECTED-FAIL | tests/test-windows.testWindowIteratorPrivateDefault | false != true

Categories

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

Product:
Add-on SDK Graveyard
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 866323

People

(Reporter: evold, Assigned: evold)

References

(Depends on 1 open bug)

Details

(Keywords: intermittent-failure)

Attachments

(2 files)

Pointer to Github pull request: https://github.com/mozilla/addon-sdk/pull/828
355 bytes, text/html
mossop
: review+
Details
Pointer to Github pull request: https://github.com/mozilla/addon-sdk/pull/829
355 bytes, text/html
mossop
: review+
Details
Attachment #720148 - Flags: review?(dtownsend+bugmail)
Attachment #720148 - Flags: review?(dtownsend+bugmail) → review+
Commits pushed to master at https://github.com/mozilla/addon-sdk https://github.com/mozilla/addon-sdk/commit/b332d287bea24dd018af4eda376805eef98c207e Bug 846854: making sure that activeWindow getters have the expected window https://github.com/mozilla/addon-sdk/commit/118e3d429473d5f68ae97fd7a61fce592de3e133 Merge pull request #828 from erikvold/846854p1 Bug 846854: making sure that activeWindow getters have the expected window r=@Mossop
Attachment #720214 - Flags: review?(dtownsend+bugmail)
(Keyword needed for this to appear in TBPL bug suggestions)
Keywords: intermittent-failure
Attachment #720214 - Flags: review?(dtownsend+bugmail) → review+
Commits pushed to master at https://github.com/mozilla/addon-sdk https://github.com/mozilla/addon-sdk/commit/3fda791b1bbc1f0dca6cd64ff68481d18c9d5a0f Bug 846854: make sure that private window is focused when doing testWindowIteratorPrivateDefault https://github.com/mozilla/addon-sdk/commit/fb5726df254dc4d63bc05c7fde67badfb6659a5a Merge pull request #829 from erikvold/846854p2 Bug 846854: make sure that private window is focused when doing testWindowIteratorPrivateDefault r=@Mossop
This looks fixed to me now.
Assignee: nobody → evold
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Depends on: 848116
(In reply to Erik Vold [:erikvold] [:ztatic] from comment #6) > This looks fixed to me now. Ha.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Blocks: 852338
Is this still happening?
Flags: needinfo?(kwierso)
Target Milestone: --- → 1.14
(In reply to Erik Vold [:erikvold] [:ztatic] from comment #14) > Is this still happening? Looks like it's happening on Aurora, which is using whatever was uplifted most recently. Might just be something we have to deal with until 1.15's code merges down to Aurora, right Dave?
Flags: needinfo?(kwierso) → needinfo?(dtownsend+bugmail)
(In reply to Wes Kocher (:KWierso) from comment #15) > (In reply to Erik Vold [:erikvold] [:ztatic] from comment #14) > > Is this still happening? > > Looks like it's happening on Aurora, which is using whatever was uplifted > most recently. Might just be something we have to deal with until 1.15's > code merges down to Aurora, right Dave? If we can identify specific code fixes that solved this then we might be able to land it on aurora too. But if it is only a test problem then it might be easier to just wait.
Flags: needinfo?(dtownsend+bugmail)
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → DUPLICATE
The latest reports here are all 'Test run exceeded timeout (1800s)'.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: