New issue
Advanced search Search tips

Issue 718575 link

Starred by 1 user
Status: WontFix
Owner:
sprang@chromium.org
Closed: May 2017
Cc:
niklase@chromium.org
emir...@chromium.org
mflodman@chromium.org
sprang@chromium.org
brandtr@chromium.org
terelius@chromium.org
holmer@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.6% regression in browser_tests at 469303:469306

Project Member Reported by emir...@google.com, May 4 2017

Comment 1 by emir...@google.com, May 4 2017 

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

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


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

chromium-webrtc-trunk-tot-rel-mac

Comment 2 by emir...@chromium.org, May 4 2017

Cc: niklase@chromium.org

Comment 3 by emir...@chromium.org, May 4 2017

Components: Blink>WebRTC>Video

Comment 4 by sprang@chromium.org, May 5 2017

Status: WontFix (was: Assigned)
Yep, that's mine.
These test were configured with a target fps of 30, and looking at the graphs the fps has now "regressed" from hovering around 30.4fps to hovering around 30.0 fps.
I'd say my goal of making these values less inexact works well and will close as wai.
►

Sign in to add a comment