Figure out some way of reliably detecting CrOS WebRTC regressions amid the noise |
||||||
Issue descriptionWe've had our first reports of webrtc.stress CPU, and we realized we basically have no idea what to do with the data. How do we bisect into 5k+ CLs? https://bugs.chromium.org/p/chromium/issues/detail?id=670707 We need to either find a more reliable metric than CPU or write some tools to find WebRTC rolls, Chromium <video> renderer changes, etc.
,
Dec 14 2016
,
Aug 2 2017
I have a feeling we've improved here, but CC'ing some folks just in case. Can we close this?
,
Aug 2 2017
ehmaldonado, kjellander, how is this going?
,
Aug 15 2017
AFAIK we have auto-bisection into WebRTC rolls for the bots in chromium.perf now, but I'm not sure it has actually been used in a real-world regression yet. Edward do you know? Other than that, Edward has been working on improving our performance tests a lot the past year, so I'll leave it to him to comment here and possibly closing this bug as Fixed/WontFix.
,
Dec 13 2017
I'm going to proactively close as fixed.
,
Jul 30
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by phoglund@chromium.org
, Dec 5 2016