Open
Bug 962662
Opened 11 years ago
Updated 2 years ago
add support for dumping CC logs after each mochitest
Categories
(Testing :: Mochitest, defect)
Testing
Mochitest
Tracking
(Not tracked)
NEW
People
(Reporter: froydnj, Unassigned)
References
Details
Adding to the about:memory and DMD logs that we are already capable of dumping, let's add CC logs, too. You can, of course, dump logs manually, but I just tried that with --keep-open and now I have no idea where my logs wound up (on Windows).
Adding CC log dumping is not as straightforward as adding the other two, because the CC logging bits don't let us specify a file on a per-dump basis. Also, triggering the appropriate collections doesn't expose the logging interfaces to JS AFAICS. So we'll have to do more work there.
![]() |
||
Comment 1•11 years ago
|
||
I'm not sure if this relates to bug 903131 or not.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•