Issue metadata
Sign in to add a comment
|
1.9%-811.6% regression in browser_tests at 429843:430571 |
||||||||||||||||||||
Issue descriptionI suspect https://chromium.googlesource.com/chromium/src/+/3c3e253cdc8ee3cde7b76c80e205eb3f86eae833 ("Roll OpenH264 from v1.4.1 to v1.6.0"). sprang@, please, mark as WAI if expected.
,
Nov 16 2016
Hm, not so sure. There seems to be regressions in a number of non H264-related tests. Such as a similar huge spike in BWE for ChromiumWebRTC/chromium-webrtc-rel-7/browser_tests / bwe_stats_VP8 / available_send_bw There also a curiously large range for this data point: Chromium Commit Position range: 429861 - 430548 For most other data point there seems to be anywhere from a single one to 30 or so revisions. Not almost 700... For now, assigning back for further triaging.
,
Nov 18 2016
,
Nov 22 2016
Ping? I'm a little worried about this one. I think it made M56 cut as well? Looks bwe-related to me. terelius@, can you have a look?
,
Dec 6 2016
Is this caused by https://codereview.webrtc.org/2430133005 ?
,
Mar 6 2017
What happened to this one? Removing R-V-G label (was set upon bug filing because the bot was incorrectly configured as internal)
,
Mar 17 2017
I believe this is fixed now |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by hlundin@chromium.org
, Nov 16 2016