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

Issue 847504 link

Starred by 1 user
Status: Assigned
Owner:
thakis@chromium.org
Cc:
thakis@chromium.org
█ kraynov@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.1% regression in thread_times.key_silk_cases at 560546:560675

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

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

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

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


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

android-one
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 3 2018

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

Make components behave the same on android and elsewhere. by thakis@chromium.org
https://chromium.googlesource.com/chromium/src/+/0ffeb3f08464644582f40e9e7c41ffdfab00a836
4.167 → 4.277 (+0.1103)

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

Sign in to add a comment