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)
Remote Protocol
Marionette
Tracking
(firefox38 affected, firefox39 fixed)
RESOLVED
FIXED
mozilla39
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.
Assignee | ||
Comment 1•9 years ago
|
||
/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)
Assignee | ||
Comment 2•9 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=321f37f2d138
Comment 3•9 years ago
|
||
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?
Updated•9 years ago
|
Attachment #8579657 -
Flags: review?(dave.hunt)
Comment 4•9 years ago
|
||
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?
Comment 5•9 years ago
|
||
Hm, how is this related to bug 1141519? David, maybe you can give an answer before Chris comes online later today?
Blocks: m21s
status-firefox38:
--- → affected
status-firefox39:
--- → affected
Flags: needinfo?(dburns)
OS: Linux → All
Hardware: x86_64 → All
Comment 6•9 years ago
|
||
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)
Assignee | ||
Comment 7•9 years ago
|
||
(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
Assignee | ||
Comment 8•9 years ago
|
||
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 9•9 years ago
|
||
Comment on attachment 8579657 [details] MozReview Request: bz://1144907/chmanchester https://reviewboard.mozilla.org/r/5671/#review4687 Ship It!
Attachment #8579657 -
Flags: review+
Assignee | ||
Comment 10•9 years ago
|
||
Try in comment 7 and comment 2. The jobs that failed in comment 7 don't run this code.
Keywords: checkin-needed
Comment 11•9 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/f709311934dc
Flags: in-testsuite+
Keywords: checkin-needed
Comment 12•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/f709311934dc
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla39
Assignee | ||
Comment 13•9 years ago
|
||
Attachment #8579657 -
Attachment is obsolete: true
Attachment #8619804 -
Flags: review+
Assignee | ||
Comment 14•9 years ago
|
||
Updated•1 year ago
|
Product: Testing → Remote Protocol
You need to log in
before you can comment on or make changes to this bug.
Description
•