Closed Bug 920354 Opened 8 years ago Closed 8 years ago

Schedule b2g desktop mochitests on Cedar and Ash

Categories

(Release Engineering :: General, defect)

All
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ahal, Unassigned)

References

Details

Attachments

(1 file)

Once bug 916119 lands we need to schedule b2g desktop mochitests on cedar.
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
We'll also need to move the b2g desktop builds out of the umbrella of the linux platform to make the results less confusing.
(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.
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.
Component: Release Automation → General Automation
QA Contact: bhearsum → catlee
With bug 916119 landed we can move ahead with this.
Blocks: 916127
Attached patch cedar_and_ashSplinter Review
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)
(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 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+
(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.
in production
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.