New issue
Advanced search Search tips

Issue 829407 link

Starred by 1 user
Status: Assigned
Owner:
dtu@chromium.org
Cc:
fmea...@chromium.org
kojii@chromium.org
eyaich@google.com
jbudorick@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

151.3%-363% regression in loading.desktop at 547688:547886

Project Member Reported by fmea...@chromium.org, Apr 5 2018 
See the link to graphs below.
Project Member

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

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

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


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

chromium-rel-win10
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
Project Member

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

Cc: eyaich@google.com jbudorick@chromium.org kojii@chromium.org
Status: Assigned (was: Untriaged)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/14920748c40000

[auto] Update FlagExpectations for LayoutNG by kojii@chromium.org
https://chromium.googlesource.com/chromium/src/+/1a9435a415786c0f2f57c3ed443631584efd245a

Updating mb configs with new builder names by eyaich@google.com
https://chromium.googlesource.com/chromium/src/+/87787af4d4d7bfd7b4ba255e7c1a01f46066b29d

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

Comment 6 by sullivan@google.com, May 9 2018

Owner: dtu@chromium.org
Dave, the pinpoint graph is really hard to read. The CLs blamed look like there's a breakage and not a perf regression?

Comment 7 by dtu@chromium.org, May 19 2018 

Filed a bug for the graphs. https://github.com/catapult-project/catapult/issues/4472
►

Sign in to add a comment