Closed Bug 1149347 Opened 10 years ago Closed 10 years ago

Don't initialize SpecialPowers in server.js

Categories

(Remote Protocol :: Marionette, defect)

Product:
Remote Protocol
Component:
Marionette
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox40 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla40
Tracking Flags:
Tracking Status
firefox40 --- fixed

People

(Reporter: jgriffin, Assigned: jgriffin)

Details

Attachments

(1 file)

Don't initialize SpecialPowers unconditionally,
1.44 KB, patch
ato
: review+
Details | Diff | Splinter Review
The recent refactor of Marionette caused us to revert some recent changes in SpecialPowers initialization in Marionette. I'll put up a patch to fix that.
Here's a try run to show this is harmless: https://treeherder.mozilla.org/#/jobs?repo=try&revision=fdfd99dedb15 The Gip failures all seem related to unrelated issues, possibly TaskCluster.
Attachment #8585774 - Flags: review?(ato)
Attachment #8585774 - Flags: review?(ato) → review+
https://hg.mozilla.org/mozilla-central/rev/01992671dc61
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
status-firefox40: --- → fixed
Resolution: --- → FIXED
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: