Closed
Bug 1116275
Opened 10 years ago
Closed 7 years ago
Allow specifying test jobs to not be run by default on try
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: armenzg, Unassigned)
Details
We have this ability for builds but not for tests:
> I looked into this recently, and there's an easy config option for making
> builds non-default:
> http://mxr.mozilla.org/build/source/buildbot-configs/mozilla/config.py#679
Comment 1•10 years ago
|
||
catlee would like this to exist, because he would like to make the non-mochitest version of Jetpack and Android jittests non-default.
Comment 2•10 years ago
|
||
I would like this to enable wpt-debug on try, but non-default, so I can stabilise it without wasting huge amounts of time and money running on cedar.
Reporter | ||
Comment 3•9 years ago
|
||
Filed bug 1198430 as a way to fix this without trying to fix it in buildbot-configs.
Comment 4•9 years ago
|
||
I would also like this for mochitest-browser-chrome so we aren't taking screenshots and storing them in S3 for try pushers who aren't going to look at them.
Reporter | ||
Comment 5•9 years ago
|
||
I don't expect anyone working on this since we're trying to reduce investment in the Buildbot set up.
Bug 1244176 is the equivalent one for TaskCluster and that will probably work.
Assignee | ||
Updated•8 years ago
|
Component: Tools → General
Comment 6•7 years ago
|
||
I think ./mach try fuzzy has removed the need for this.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•