New issue
Advanced search Search tips

Issue 850421 link

Starred by 1 user
Status: WontFix
Owner:
jarin@chromium.org
Closed: Jul 16
Cc:
jarin@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.6% regression in speedometer at 564847:564902

Project Member Reported by jarin@google.com, Jun 7 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 7 2018 

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

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


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

linux-perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 7 2018

Cc: rjkroege@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11b97001240000

[ozone] Added docs for building/running CrOS/Chrome on Linux by rjkroege@chromium.org
https://chromium.googlesource.com/chromium/src/+/d5bec62f900f409f787852da98d85f04099a6554
486.2 → 513.2 (+26.98)

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

Comment 4 by rjkroege@chromium.org, Jun 7 2018

Cc: -rjkroege@chromium.org
Removing myself as my CL was documentation only.

Comment 5 by jarin@chromium.org, Jul 16

Status: WontFix (was: Assigned)
►

Sign in to add a comment