New issue
Advanced search Search tips

Issue 671220 link

Starred by 1 user
Status: WontFix
Owner:
sergeyu@chromium.org
Closed: Dec 2016
Cc:
terelius@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

164.9% regression in webrtc_perf_tests at 15392:15392

Project Member Reported by terelius@chromium.org, Dec 5 2016 
Please investigate whether this is a real regression and whether it is related to your CL https://codereview.webrtc.org/2546613003

Comment 1 by terelius@chromium.org, Dec 5 2016 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=671220

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgp8WsuQoM


Bot(s) for this bug's original alert(s):

webrtc-linux-large-tests

Comment 2 by brandtr@chromium.org, Dec 13 2016 

The following metric

ChromiumWebRTC/chromium-webrtc-rel-win10/browser_tests / video_cpu_usage_VP9 / goog_encode_usage_percent

has recovered. I've added it to the group report.

Comment 3 by sergeyu@chromium.org, Dec 18 2016

Status: WontFix (was: Assigned)
This was a fix for bug 669421
►

Sign in to add a comment