New issue
Advanced search Search tips

Issue 844601 link

Starred by 1 user
Status: WontFix
Owner:
wangxianzhu@chromium.org
Closed: May 2018
Cc:
wangxianzhu@chromium.org
npm@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

14.6%-31.2% regression in thread_times.key_silk_cases at 558380:558585

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

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

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

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


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

android-nexus5
android-nexus5X
Project Member

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

Cc: wangxianzhu@chromium.org
Owner: wangxianzhu@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12ccc154240000

[PE] Fix border-radius with overflow-clip without visual overflow by wangxianzhu@chromium.org
https://chromium.googlesource.com/chromium/src/+/e2cfcd78b0b762eea5eaffec65ed2f217e179403

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

Comment 4 by wangxianzhu@chromium.org, May 21 2018

Status: WontFix (was: Assigned)
The CL fixed a bug that caused the false performance progression.
►

Sign in to add a comment