Closed
Bug 1486817
Opened 7 years ago
Closed 7 years ago
Use separate log modules for mediapipeline and rtplogger
Categories
(Core :: WebRTC: Signaling, enhancement, P2)
Tracking
()
RESOLVED
FIXED
mozilla63
| Tracking | Status | |
|---|---|---|
| firefox63 | --- | fixed |
People
(Reporter: dminor, Assigned: dminor)
References
Details
Attachments
(1 file)
Bug 1402334 merged the mediapipeline and RtpLogger logs with the signaling logs. The resulting logs are too large, we should break them back out into separate log modules.
|
Assignee | |
Updated•7 years ago
|
Assignee: nobody → dminor
Status: NEW → ASSIGNED
Rank: 15
|
|
Assignee | |
Comment 1•7 years ago
|
||
|
|
Assignee | |
Comment 2•7 years ago
|
||
This restores the separate mediapipeline and RtpLogger lazy log modules that
were unified with the Signaling log module in Bug 1402334.
|
||
Comment 3•7 years ago
|
||
Comment on attachment 9004660 [details]
Bug 1486817 - Use separate log modules for mediapipeline and rtplogger; r=bwc
Byron Campen [:bwc] has approved the revision.
Attachment #9004660 -
Flags: review+
Pushed by dminor@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f8c805ba9071
Use separate log modules for mediapipeline and rtplogger; r=bwc
|
||
Comment 5•7 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in
before you can comment on or make changes to this bug.
Description
•