New issue
Advanced search Search tips

Issue 687044 link

Starred by 1 user
Status: WontFix
Owner:
peah@chromium.org
Closed: Feb 2017
Cc:
peah@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

36.6% regression in webrtc_perf_tests at 15996:15996

Project Member Reported by peah@chromium.org, Jan 31 2017 
See the link to graphs below.

Comment 1 by peah@chromium.org, Jan 31 2017 

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

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


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

webrtc-win-large-tests

Comment 2 by peah@chromium.org, Jan 31 2017

Owner: philipel@chromium.org
philipel@: Could this be related to your CL https://codereview.webrtc.org/2656983002?

Comment 3 by philipel@chromium.org, Jan 31 2017

Owner: peah@chromium.org
Sorry, don't think this one is related to the new jitter buffer. It looks like the regression was introduced by the Chromium roll, and then fixed by the Chromium roll just after the metric went down again.

Comment 4 by peah@chromium.org, Feb 2 2017

Status: WontFix (was: Untriaged)
Thanks for checking! Since the regression was fixed by the next roll, I'll close as wontfix.
►

Sign in to add a comment