Closed
Bug 774827
Opened 12 years ago
Closed 10 years ago
cfx testall --logfile=FOO doesn't work the way it should
Categories
(Add-on SDK Graveyard :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: KWierso, Unassigned)
References
Details
Aside from the timeouts in bug 774821, there's further issues with using --logfile when using cfx testall instead of cfx test. The way it should work is that as you test each package, the logs get appended to the logfile, so that when testall finishes testing everything, the logfile has logs from every package that was tested. The way it currently works, every time cfx moves on to the next package, the logfile is deleted and recreated as an empty text file, so that when testall finishes, it only contains the logs from the most recently tested package.
Reporter | ||
Updated•12 years ago
|
Priority: -- → P3
Reporter | ||
Comment 1•12 years ago
|
||
So, something has changed recently with this (probably the new module layout?). Whereas before, "cfx testall --logfile FOO" would finish up with just the most recent package logged in the logfile, it now finishes the tests, and then the logfile is deleted, so we get nothing. This now also seems to affect "cfx test --logfile FOO", at least when it is run from the test/ directory.
Reporter | ||
Comment 3•10 years ago
|
||
I don't use this at all, but it was defined in cfx's documentation, and didn't really work as described.
Flags: needinfo?(kwierso)
Comment 4•10 years ago
|
||
Sorry we won't be releasing any new versions of cfx, jpm is the replacement https://www.npmjs.com/package/jpm
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•