Closed
Bug 915014
Opened 11 years ago
Closed 11 years ago
"Ci is not defined" during B2G desktop mochitests
Categories
(Testing :: Mochitest, defect)
Testing
Mochitest
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla26
People
(Reporter: jgriffin, Assigned: jgriffin)
Details
Attachments
(1 file)
807 bytes,
patch
|
jmaher
:
review+
|
Details | Diff | Splinter Review |
When running mochitests on B2G desktop builds, we get the following error: System JS : ERROR chrome://specialpowers/content/SpecialPowersObserverAPI.js:102 ReferenceError: Ci is not defined This has to do with B2G compartment sharing and not inheriting the definition of Ci from the parent context.
Assignee | ||
Comment 1•11 years ago
|
||
Attachment #802843 -
Flags: review?(jmaher)
Assignee | ||
Comment 2•11 years ago
|
||
try: https://tbpl.mozilla.org/?tree=Try&rev=23a632524dd3
Comment 3•11 years ago
|
||
Comment on attachment 802843 [details] [diff] [review] Define CI Review of attachment 802843 [details] [diff] [review]: ----------------------------------------------------------------- ::: testing/specialpowers/content/SpecialPowersObserverAPI.js @@ +5,5 @@ > Components.utils.import("resource://gre/modules/Services.jsm"); > > +if (typeof(Ci) == 'undefined') { > + const Ci = Components.interfaces; > +} I recall an issue in the past where detecting this for CC required a try/catch. If you have tested this and it works for the case where it was undefined, then all is well.
Attachment #802843 -
Flags: review?(jmaher) → review+
Assignee | ||
Comment 4•11 years ago
|
||
Yep it works, thanks.
Assignee | ||
Comment 5•11 years ago
|
||
Last try job was causing some "redefinition of Ci" errors on desktop; here's a new one that passes for me locally: https://tbpl.mozilla.org/?tree=Try&rev=3b1351ba4e4f
Assignee | ||
Comment 6•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/bc729c5726bb
Target Milestone: --- → mozilla26
Comment 7•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/bc729c5726bb
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•