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

Issue 826803 link

Starred by 1 user
Status: WontFix
Owner:
mythria@chromium.org
Closed: May 2018
Cc:
█ catapult...@skia-buildbots.google.com.iam.gserviceaccount.com
npm@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.3%-466% regression in system_health.common_desktop at 542843:543139

Project Member Reported by npm@chromium.org, Mar 28 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Mar 28 2018 

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

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


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

linux-release
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Mar 28 2018

Cc: catapult...@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/14dec607440000

Roll src/third_party/catapult/ 7b53f088f..f73167a68 (1 commit) by catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/320ac37b57c63feeac20bd169d80efdaa4c0a298

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

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

Owner: mythria@chromium.org
mythria: the only CL in that catapult roll is "Ignore i-frame navigationStart events when computing LoadExpectation". Is this expected?

Comment 5 by mythria@chromium.org, May 1 2018

Status: WontFix (was: Assigned)
I am sorry somehow missed this. Yes, that would have caused changes to the loading metrics. Since we now ignore i-frames not corresponding to the main events, which could cause differences in what we measure. Marking it as won't fix.
►

Sign in to add a comment