New issue
Advanced search Search tips

Issue 843619 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 843618
Owner:
Closed: Jul 18
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

25.8% regression in system_health.common_desktop at 547881:554637

Project Member Reported by chiniforooshan@chromium.org, May 16 2018

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

win-high-dpi
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 18 2018

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/11fcd028240000

__init__() got an unexpected keyword argument 'scope'
Cc: pmonette@chromium.org
Owner: pmonette@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14fb49eea40000

Adding fieldtrial config for the IncompatibleApplicationsWarning feature by pmonette@chromium.org
https://chromium.googlesource.com/chromium/src/+/7a86e22e588d7941bde54bdb4a8c58c23e502836
0.4735 → 0.5743 (+0.1008)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Mergedinto: 843618
Status: Duplicate (was: Assigned)

Sign in to add a comment