Closed
Bug 1042270
Opened 10 years ago
Closed 10 years ago
Add Mulet compatibility to mochitest mach target
Categories
(Testing :: Mochitest, defect)
Testing
Mochitest
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla34
People
(Reporter: jgriffin, Assigned: jgriffin)
References
Details
Attachments
(1 file)
1.58 KB,
patch
|
ahal
:
review+
|
Details | Diff | Splinter Review |
We're nearly ready to enable Mulet builds and mochitests across trunk branches, but we need to make sure developers can run the tests easily. Currently, ./mach mochitest-plain fails on mulet with the error: It looks like you tried to run a mach command from an invalid context. The mochitest-plain command failed to meet the following conditions: is_firefox - Must have a Firefox build.
Assignee | ||
Comment 1•10 years ago
|
||
With this, mochitest-plain works fine locally with mach.
Attachment #8460567 -
Flags: review?(ahalberstadt)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → jgriffin
Comment 2•10 years ago
|
||
Comment on attachment 8460567 [details] [diff] [review] Add is_mulet condition to mach, Review of attachment 8460567 [details] [diff] [review]: ----------------------------------------------------------------- Nice that it works out of the box! ::: python/mozbuild/mozbuild/base.py @@ +619,5 @@ > + return cls.substs.get('MOZ_BUILD_APP') == 'b2g/dev' > + return False > + > + @staticmethod > + def is_firefox_or_mulet(cls): Personally I would define is_firefox_or_mulet in the mach_commands.py instead of here, but I guess if it will be used frequently by several different mach_commands.py files, then it's ok.
Attachment #8460567 -
Flags: review?(ahalberstadt) → review+
Assignee | ||
Comment 3•10 years ago
|
||
It will be used in probably three different mach_commands.py files, so leaving as-is. https://hg.mozilla.org/integration/mozilla-inbound/rev/9c86306df8c2
Target Milestone: --- → mozilla34
Comment 4•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/9c86306df8c2
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•