Closed
Bug 1291486
Opened 8 years ago
Closed 5 years ago
offer a way to not rerun (xpcshell) test failures (and/or inspect the output from such failed tests)
Categories
(Testing :: XPCShell Harness, defect, P3)
Testing
XPCShell Harness
Tracking
(firefox51 wontfix, firefox69 fixed)
RESOLVED
FIXED
mozilla69
People
(Reporter: keeler, Assigned: standard8)
Details
Attachments
(1 file)
If I run `./mach xpcshell-test security/manager/ssl/tests/unit/`, test_pkcs11_insert_remove.js will consistently fail when run in parallel, but it will always succeed when rerun by mach (or xpcshell - I'm not actually sure who's doing what here). I would like to know why it failed, but mach (or xpcshell - again I'm not sure who's in charge here) doesn't give me any informative output (because, after all, everything eventually succeeded). I guess either I want a way to look at the output from the original failing test or to have mach/xpcshell treat that failure as a failure and dump the output from it.
Reporter | ||
Comment 1•8 years ago
|
||
Oh, I guess there's '--verbose', but that gives me way too much output - I really only want the output from the failing test.
Updated•8 years ago
|
Component: mach → XPCShell Harness
Product: Core → Testing
Updated•6 years ago
|
Priority: -- → P3
Assignee | ||
Comment 2•5 years ago
|
||
I think I know a way of doing this, just have to figure out how to get an appropriate argument into it.
How about --verbose-if-fails
?
Assignee | ||
Updated•5 years ago
|
Assignee: nobody → standard8
Assignee | ||
Comment 3•5 years ago
|
||
When running xpcshell-tests, if a test fails when run in parallel, and then passes when re-run sequentially, the log cannot be seen. Verbose mode is not good enough as that interweaves all the logs.
This adds an option that allows printing only the log of the test that fails.
Pushed by mbanner@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/3565a43b5387 Add an option (--verbose-if-fails) to mach's xpcshell-test to output test log if it fails when it will be retried. r=ahal
Comment 5•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox69:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
Updated•5 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•