Closed
Bug 920354
Opened 11 years ago
Closed 11 years ago
Schedule b2g desktop mochitests on Cedar and Ash
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ahal, Unassigned)
References
Details
Attachments
(1 file)
(deleted),
patch
|
mozilla
:
review+
mozilla
:
feedback+
ahal
:
checked-in+
|
Details | Diff | Splinter Review |
Once bug 916119 lands we need to schedule b2g desktop mochitests on cedar.
Reporter | ||
Comment 1•11 years ago
|
||
Also would be nice to have on ash to help debug any mozharness issues I might run into.
Summary: Schedule b2g desktop mochitests on Cedar → Schedule b2g desktop mochitests on Cedar and Ash
Reporter | ||
Comment 2•11 years ago
|
||
We'll also need to move the b2g desktop builds out of the umbrella of the linux platform to make the results less confusing.
Comment 3•11 years ago
|
||
(In reply to Andrew Halberstadt [:ahal] from comment #2)
> We'll also need to move the b2g desktop builds out of the umbrella of the
> linux platform to make the results less confusing.
See bug 916927. Note comment 1 as you're moving forward here.
Reporter | ||
Comment 4•11 years ago
|
||
Great. Bug 916927 doesn't necessarily block this bug (I can working on greening up the suite in parallel to it), but it would be nice to have.
Updated•11 years ago
|
Component: Release Automation → General Automation
QA Contact: bhearsum → catlee
Reporter | ||
Comment 6•11 years ago
|
||
I think this patch is what we need, though imo the b2g_config.py file is starting to get really messy. For one, I had to create a new unittest called MOCHITEST_PLAIN because the current testsuite vars are tied to a particular mozharness script. Therefore feel free to use this as a guideline and refactor the file a different way if you wish. I don't want to change things around too much as I'm not the one who has to use it all the time :)
Another unrelated thing that confused me was http://mxr.mozilla.org/build/source/buildbot-configs/mozilla-tests/b2g_config.py#1140 .. it looks like linux32_gecko is still running on all branches?
Attachment #812141 -
Flags: feedback?(aki)
Comment 7•11 years ago
|
||
(In reply to Andrew Halberstadt [:ahal] from comment #6)
> Another unrelated thing that confused me was
> http://mxr.mozilla.org/build/source/buildbot-configs/mozilla-tests/
> b2g_config.py#1140 .. it looks like linux32_gecko is still running on all
> branches?
linux32_gecko is still running where?
Note, this is the test config, so builds are still running elsewhere.
Comment 8•11 years ago
|
||
Comment on attachment 812141 [details] [diff] [review]
cedar_and_ash
I'm not sure it's clear what's different between MOCHITEST and MOCHITEST_PLAIN.
Maybe call it MOCHITEST_DESKTOP ?
Attachment #812141 -
Flags: feedback?(aki) → feedback+
Updated•11 years ago
|
Attachment #812141 -
Flags: review+
Reporter | ||
Comment 9•11 years ago
|
||
(In reply to Aki Sasaki [:aki] from comment #7)
> linux32_gecko is still running where?
> Note, this is the test config, so builds are still running elsewhere.
Oh right, nvm.
Reporter | ||
Comment 10•11 years ago
|
||
Comment on attachment 812141 [details] [diff] [review]
cedar_and_ash
https://hg.mozilla.org/build/buildbot-configs/rev/a76a8bf52414
Attachment #812141 -
Flags: checked-in+
Comment 11•11 years ago
|
||
in production
Reporter | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•