Issue metadata
Sign in to add a comment
|
9% regression in webrtc_perf_tests at 16626:16627 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 17 2017
I would guess it's due to this CL: https://chromium.googlesource.com/external/webrtc/+/280eb224e2e0630ec94a6072777d58354357ee67 but I also think It might be due to this CL (the build before the alert): https://chromium.googlesource.com/external/webrtc/+/2a8c2f589aa5e757cdb5d5cbb13f4494250ddf11 since there was a similar change in metrics when this CL landed: https://chromium.googlesource.com/external/webrtc/+/5f4712686550ba1d069c5e4c456ffcabe7ccba97
,
Feb 17 2017
I don't think NetEq is even included in the apm_timing tests. This would exclude https://chromium.googlesource.com/external/webrtc/+/280eb224e2e0630ec94a6072777d58354357ee67.
,
Mar 2 2017
My changes could not possibly affect these tests. Closing this, as stats returned to normal by themselves. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by philipel@chromium.org
, Feb 17 2017