Closed Bug 1144907 Opened 9 years ago Closed 9 years ago

Marionette's gather_debug shouldn't leave calling code in content scope if it didn't start there

Categories

(Remote Protocol :: Marionette, defect)

defect
Not set
normal

Tracking

(firefox38 affected, firefox39 fixed)

RESOLVED FIXED
mozilla39
Tracking Status
firefox38 --- affected
firefox39 --- fixed

People

(Reporter: chmanchester, Assigned: chmanchester)

References

Details

Attachments

(1 file, 1 obsolete file)

We can use using_context so callers in chrome scope can be sure their tearDown code runs in the correct scope when a test is skipped or fails.
/r/5673 - Bug 1144907 - Restore previous context after calling marionette's gather_debug.;r=davehunt

Pull down this commit:

hg pull review -r 7dde4d7281c39f7e39e0eaf7dfca1448fd25c172
Attachment #8579657 - Flags: review?(dave.hunt)
I'm not familiar with MozReview. I've left a comment. Could you include the Gip tests (gaia-ui-test-accessibility,gaia-ui-test-unit,gaia-ui-test-functional-1,gaia-ui-test-functional-2,gaia-ui-test-functional-3) in your try run?
Attachment #8579657 - Flags: review?(dave.hunt)
Comment on attachment 8579657 [details]
MozReview Request: bz://1144907/chmanchester

https://reviewboard.mozilla.org/r/5671/#review4643

::: testing/marionette/client/marionette/runner/base.py
(Diff revision 1)
> -                    marionette.set_context(marionette.CONTEXT_CONTENT)
> +                    with marionette.using_context(marionette.CONTEXT_CONTENT):

Can we not combine these into a single using_context?
Hm, how is this related to bug 1141519? David, maybe you can give an answer before Chris comes online later today?
Blocks: m21s
Flags: needinfo?(dburns)
OS: Linux → All
Hardware: x86_64 → All
They are not related. Since we are still using content this patch would still hit the issue that we see in bug 1141519
Flags: needinfo?(dburns)
(In reply to Dave Hunt (:davehunt) from comment #3)
> I'm not familiar with MozReview. I've left a comment. Could you include the
> Gip tests
> (gaia-ui-test-accessibility,gaia-ui-test-unit,gaia-ui-test-functional-1,gaia-
> ui-test-functional-2,gaia-ui-test-functional-3) in your try run?

Certainly: https://treeherder.mozilla.org/#/jobs?repo=try&revision=69ab6eafda85
https://reviewboard.mozilla.org/r/5671/#review4677

> Can we not combine these into a single using_context?

It seems that getting a screenshot is really intended to work in chrome, and getting the page source is really intended to work in content, so if we don't have using_context for each either callers in chrome or callers in content aren't going to get what they expect.
Comment on attachment 8579657 [details]
MozReview Request: bz://1144907/chmanchester

https://reviewboard.mozilla.org/r/5671/#review4687

Ship It!
Attachment #8579657 - Flags: review+
Try in comment 7 and comment 2. The jobs that failed in comment 7 don't run this code.
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/f709311934dc
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla39
Attachment #8579657 - Attachment is obsolete: true
Attachment #8619804 - Flags: review+
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: