New issue
Advanced search Search tips

Issue 830779 link

Starred by 1 user
Status: Duplicate
Merged: issue 817942
Owner:
primiano@chromium.org
Closed: Apr 2018
Cc:
bajones@chromium.org
fmalita@chromium.org
liyuqian@google.com
primiano@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

14.9% regression in thread_times.key_silk_cases at 548116:548226

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

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

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

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


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

android-nexus6
Project Member

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

Cc: bajones@chromium.org fmalita@chromium.org liyuqian@google.com
Owner: liyuqian@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16fa746cc40000

Remove SK_SUPPORT_LEGACY_AA_CHOICE and rebaseline by liyuqian@google.com
https://chromium.googlesource.com/chromium/src/+/26de0ebc954e8df16905f6e25698c12a79ba6b94

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

Comment 4 by liyuqian@google.com, Apr 10 2018

Owner: primiano@chromium.org
This seems to be a duplicate of  crbug.com/817942 

The CL "Remove SK_SUPPORT_LEGACY_AA_CHOICE and rebaseline" is very old so why is it only discovered now? Even the fix should have already been merged and you can see that the graph in  crbug.com/817942  has already stepped down.

Comment 5 by primiano@chromium.org, Apr 30 2018

Mergedinto: 817942
Status: Duplicate (was: Assigned)
►

Sign in to add a comment