46 bytes, text/x-phabricator-request
|Details | Review|
Looking at https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2018-03-14&include_spill=0&keys=__none__!__none__!__none__&max_channel_version=nightly%252F60&measure=WEBRTC_DATACHANNEL_NEGOTIATED&min_channel_version=null&processType=*&product=Firefox&sanitize=0&sort_keys=submissions&start_date=2018-01-22&table=1&trim=0&use_submission_date=0 from Nightly 60 on WEBRTC_DATACHANNEL_NEGOTIATED only ever reports no data channel at all. My guess is that something in 59, probably Transceivers, broke this stat.
I also tested this locally by doing a Datachannel only PeerConnection and checking about:telemetry before and after. And the count for WEBRTC_DATACHANNEL_NEGOTIATED went up by on for no data channel, even though only a data channel got established.
Byron could you please have a look how this would be to fix?
This doesn't look very hard.
Assignee: nobody → docfaraday
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/18725d7ee61d Count datachannel "tracks" properly again. r=mjf
You need to log in before you can comment on or make changes to this bug.