New issue
Advanced search Search tips

Issue 847165 link

Starred by 1 user
Status: Fixed
Owner: ----
Closed: Jul 2
Cc:
petermarshall@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.2%-16.3% regression in v8.browsing_desktop at 552589:552593

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

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

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

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


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

linux-perf
Project Member

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

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

All of the attempts failed. See the individual attempts for details on each error.
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Jun 11 2018 

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

All of the runs failed. The most common error (19/20 runs) was:
Exception: Shard indicators must be present for perf tests
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Jun 11 2018 

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

All of the runs failed. The most common error (18/20 runs) was:
Exception: Shard indicators must be present for perf tests
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Jun 11 2018 

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

All of the runs failed. The most common error (20/20 runs) was:
Exception: Shard indicators must be present for perf tests

Comment 10 by petermarshall@chromium.org, Jul 2

Status: Fixed (was: Untriaged)
Looks embedded builtin related, recovered, unbisectable
►

Sign in to add a comment