Closed
Bug 618958
Opened 14 years ago
Closed 11 years ago
[sychronization] buildbotcustom should run mozmill tests in a better way
Categories
(Testing Graveyard :: Mozmill, defect)
Testing Graveyard
Mozmill
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: k0scist, Unassigned)
References
Details
with the coming of mozmill 1.5.2 and bug 613804 (`make mozmill`),
mozmill will have manifests, so the buildbotcustom code should be
updated to run with manifests. In addition, currently the paths to
mozmill and mozmill-restart are coded as logic inside buildbotcustom:
http://hg.mozilla.org/build/buildbotcustom/file/c28f34b98879/steps/unittest.py#l261
bug 613804 will introduce wrappers for this in m-c which should be
utilized instead
Reporter | ||
Updated•14 years ago
|
Reporter | ||
Updated•14 years ago
|
Summary: buildbotcustom should run mozmill tests in a better way → [sychronization] buildbotcustom should run mozmill tests in a better way
Reporter | ||
Updated•14 years ago
|
Assignee: nobody → jhammel
Reporter | ||
Updated•13 years ago
|
Assignee: jhammel → nobody
Comment 1•11 years ago
|
||
There are no plans at the moment in trying to get mozmill running on buildbot again. So closing.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
Assignee | ||
Updated•8 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•