Closed
Bug 610413
Opened 14 years ago
Closed 13 years ago
Make sure TryChooser and friends understand Mozmill
Categories
(Release Engineering :: General, defect, P5)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jhford, Unassigned)
References
Details
(Whiteboard: [trychooser][unittest])
mozmill-all is now a unit test suite. The TryChooser should be able to allow try server jobs to get mozmill coverage.
Updated•14 years ago
|
Whiteboard: [trychooser][mozmill]
Updated•14 years ago
|
Whiteboard: [trychooser][mozmill] → [trychooser]
Updated•14 years ago
|
Priority: -- → P5
Comment 1•14 years ago
|
||
The landing of bug 585370 broke Mozmill on mozilla-central, because tests cannot be run on tryserver yet. To stop that in the future we should have tryserver support for Mozmill ASAP.
When will RelEng be able to add this feature?
Comment 4•14 years ago
|
||
Please stop changing flags. This has to be done by someone from RelEng.
Priority: P1 → P5
How can we help with this? I believe this [1] is the code that needs to change, correct?
Is there any way to test this without running it in RelEng Staging?
[1]: http://mxr.mozilla.org/build/source/buildbotcustom/try_parser.py
Updated•14 years ago
|
Whiteboard: [trychooser] → [trychooser][unittest]
Comment 6•13 years ago
|
||
The mozmill-all suite was disabled in bug 630551 but try should be able to accept the syntax for a mozmill-all test suite automatically when this is re-enabled. Please re-open or file a new bug if there are any issues when the suite is live again.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•