Closed
Bug 1459251
Opened 7 years ago
Closed 7 years ago
Running |mach raptor-test| with no test specified results in a traceback
Categories
(Testing :: Raptor, defect)
Tracking
(firefox62 fixed)
RESOLVED
FIXED
mozilla62
Tracking | Status | |
---|---|---|
firefox62 | --- | fixed |
People
(Reporter: ahal, Assigned: rwood)
References
Details
Attachments
(1 file)
This should probably have a better error message. Semi-relatedly, how can one fine the list of valid test names that can be passed in? It might be good to make the 'test' argument a choices action so that they can be discovered via |mach talos-test --help|.
Reporter | ||
Comment 1•7 years ago
|
||
Making it a 'choices' action would also make sure we fail fast if an invalid test were passed in (currently it does ~20 seconds worth of mozharness setup before failing).
Assignee | ||
Comment 2•7 years ago
|
||
Thanks yes I have this fixed already in the patch I'm working on for processing output. I'll move it to a separate patch here tho thanks.
Assignee | ||
Comment 3•7 years ago
|
||
(In reply to Andrew Halberstadt [:ahal] from comment #1)
> Making it a 'choices' action would also make sure we fail fast if an invalid
> test were passed in (currently it does ~20 seconds worth of mozharness setup
> before failing).
Yeah so I use manifest parser, that builds a list of available tests first. If a test argument is passed in then I check the list of tests manifest parser created. If it's in that list then it's valid, otherwise errors out invalid test. If no test is specified then all available tests will run.
Assignee | ||
Comment 4•7 years ago
|
||
Is there a way to do what you want and still use test manifests? Maybe make the test argument a choices argument but get the choices from manifest parser...
Assignee | ||
Updated•7 years ago
|
Comment hidden (mozreview-request) |
Assignee | ||
Comment 6•7 years ago
|
||
Comment on attachment 8973289 [details]
Bug 1459251 - Running |mach raptor-test| with no test specified results in a traceback;
This patch fixes the case of running:
./mach raptor-test
Now it will find and run all available tests. Note, for me on OSX, if you provide an invalid test name i.e:
./mach raptor-test invalid-test-name
It only takes 2 seconds before it errors out with:
09:58:12 INFO - manifest abort: specified test doesn't exist!
09:58:12 INFO - raptor-main abort: no tests found
09:58:12 ERROR - Return code: 1
Which is fine IMO.
Attachment #8973289 -
Flags: review?(ahalberstadt)
Comment hidden (mozreview-request) |
Assignee | ||
Comment 8•7 years ago
|
||
(In reply to Robert Wood [:rwood] from comment #6)
> ./mach raptor-test invalid-test-name
>
> It only takes 2 seconds before it errors out with:
>
> 09:58:12 INFO - manifest abort: specified test doesn't exist!
> 09:58:12 INFO - raptor-main abort: no tests found
> 09:58:12 ERROR - Return code: 1
>
> Which is fine IMO.
Ah, because I already ran Raptor previously and the raptor-venv already existed, otherwise yeah I see about 20 seconds before it errors out. I think it's fine as that's only the first time if the raptor-venv doesn't exist yet.
Comment hidden (mozreview-request) |
Assignee | ||
Comment 10•7 years ago
|
||
Reporter | ||
Comment 11•7 years ago
|
||
mozreview-review |
Comment on attachment 8973289 [details]
Bug 1459251 - Running |mach raptor-test| with no test specified results in a traceback;
https://reviewboard.mozilla.org/r/241754/#review248934
Thanks!
Attachment #8973289 -
Flags: review?(ahalberstadt) → review+
Comment 12•7 years ago
|
||
Pushed by rwood@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/fe2a0b79e7af
Running |mach raptor-test| with no test specified results in a traceback; r=ahal
Comment 13•7 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox62:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
You need to log in
before you can comment on or make changes to this bug.
Description
•