New issue
Advanced search Search tips

Issue 844439 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.1%-195.5% regression in thread_times.tough_scrolling_cases at 552286:552372

Project Member Reported by npm@chromium.org, May 18 2018

Issue description

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=844439

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


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

linux-perf
Project Member

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

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

Buildbucket says the build completed successfully, but Pinpoint can't find the isolate hash.
Project Member

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

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

Buildbucket says the build completed successfully, but Pinpoint can't find the isolate hash.

Comment 7 by bokan@chromium.org, May 31 2018

Cc: bokan@chromium.org
Status: WontFix (was: Untriaged)
On every benchmark with a ref metric, the ref metric went up an equivalent amount so it seems like not a regression in Chrome.
Issue 839754 has been merged into this issue.

Sign in to add a comment