New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 833417 link

Starred by 1 user
Status: Fixed
Owner:
g...@chromium.org
Closed: Jun 2018
Cc:
█ afdo-chr...@skia-buildbots.google.com.iam.gserviceaccount.com
sullivan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.9%-39% regression in rasterize_and_record_micro.top_25 at 549738:549816

Project Member Reported by sullivan@chromium.org, Apr 16 2018 
Splitting out from  bug 833276  since that root cause is linux-only.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Apr 16 2018 

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

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


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

android-nexus5
android-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Apr 17 2018

Cc: afdo-chr...@skia-buildbots.google.com.iam.gserviceaccount.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1193a75ac40000

Roll AFDO from 67.0.3390.0_rc-r1 to 67.0.3393.0_rc-r1 by afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/ddd73e54df17c4c75566f55cecb13a40c1e26608

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

Comment 4 by sullivan@chromium.org, Jun 1 2018

Owner: g...@chromium.org
Status: Fixed (was: Assigned)
gbiv: sorry for the late notification on this bug, the issue with not notifiying autoroll owners has since been fixed. This bug was also fixed with the roll to AFDO 68.0.3398.0_rc-r1.
►

Sign in to add a comment