Closed
Bug 1085505
Opened 10 years ago
Closed 10 years ago
gecko: mach ci-tests
Categories
(Taskcluster :: General, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jlal, Assigned: wcosta)
References
Details
Attachments
(1 file)
Along with mach ci-build we should have a mach command for running tests... This is a little more complicated since all tests need a build... To start maybe something like this: ```sh # --task-id is for picking up the correct build/tests # revision/repository should be picked up automatically from the tree # chunks should be optional but always constructed with at least one mach ci-task --task-id=x --revision=x --repository=x --total-chunks=1 --chunk=1 <test task> ```
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → wcosta
OS: Mac OS X → Linux
Priority: -- → P1
Hardware: x86 → All
Assignee | ||
Updated•10 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8516157 -
Flags: review?(jlal)
Attachment #8516157 -
Flags: review?(garndt)
Reporter | ||
Comment 2•10 years ago
|
||
Comment on attachment 8516157 [details] [review] Add "mach ci-tests" command lgtm now - tried it locally and it works well
Attachment #8516157 -
Flags: review?(jlal) → review+
Updated•10 years ago
|
Attachment #8516157 -
Flags: review?(garndt) → review+
Assignee | ||
Comment 3•10 years ago
|
||
https://github.com/lightsofapollo/gecko-dev/commit/83dd331f9de1c04d03a7fafa24236e66860f7d3b
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 4•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/25de1dc8d8ec https://hg.mozilla.org/mozilla-central/rev/a90514946a54 https://hg.mozilla.org/mozilla-central/rev/bc59c1a8fdb6
Updated•9 years ago
|
Component: TaskCluster → General
Product: Testing → Taskcluster
Target Milestone: --- → mozilla41
Version: unspecified → Trunk
Comment 5•9 years ago
|
||
Resetting Version and Target Milestone that accidentally got changed...
Target Milestone: mozilla41 → ---
Version: Trunk → unspecified
You need to log in
before you can comment on or make changes to this bug.
Description
•