New issue
Advanced search Search tips

Issue 806798 link

Starred by 1 user
Status: WontFix
Owner:
cbiesin...@chromium.org
Closed: Mar 2018
Cc:
cbiesin...@chromium.org
asvitk...@chromium.org
primiano@chromium.org
chrishtr@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.8%-44.3% regression in thread_times.key_silk_cases at 531992:532081

Project Member Reported by primiano@chromium.org, Jan 29 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 29 2018 

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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=56c4a1c1d975fc6f4dc522bf3a9500a3b33c6e96a0754c81e61a2fff6c608cba


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

android-nexus5
android-nexus5X
android-nexus6
android-nexus7v2
android-one
android-webview-nexus6

Comment 3 by vmi...@chromium.org, Feb 5 2018

Components: Internals>GPU>Metrics

Comment 5 by sullivan@chromium.org, Mar 4 2018 

Looks like the bisect repro-ed but timed out before it could narrow the range; re-running.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Mar 4 2018

Cc: cbiesin...@chromium.org chrishtr@chromium.org asvitk...@chromium.org
Owner: cbiesin...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/17112938440000

Add UKM metrics for rendering timing measurements by cbiesinger@chromium.org
https://chromium.googlesource.com/chromium/src/+/a324bac1171a6d35eb9fe367529300aabc3ae1f2

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 7 by chrishtr@chromium.org, Mar 5 2018

Status: WontFix (was: Assigned)
The patch was reverted.
►

Sign in to add a comment