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

Issue 855399 link

Starred by 1 user
Status: WontFix
Owner:
sadrul@chromium.org
Closed: Jun 2018
Cc:
sadrul@chromium.org
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

82.9% regression in system_health.common_mobile at 566634:566725

Project Member Reported by alexclarke@chromium.org, Jun 22 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 22 2018 

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

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


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

android-nexus5X
Project Member

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

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

paint timing: Use presentation-time instead of swap-time. by sadrul@chromium.org
https://chromium.googlesource.com/chromium/src/+/bf746c55adf49d2f22cc308185a16d12c4e15b04
314.9 → 675.2 (+360.3)

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

Comment 4 by sadrul@chromium.org, Jun 23 2018

Status: WontFix (was: Assigned)
timetofirst[contentful]paint is expected to go up with that change. It's not a regression (it changes how the metric is measured).
►

Sign in to add a comment