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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5KjfuwoM


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

chromium-rel-win7-single

The first bisect fails with "Failed steps failed gathering reference values.performance test 1 of 5 failed gathering reference values.reading chartjson results", and the second bisect is running.

kicked another bisect because the blocking issue was fixed

Hum... result wasn't reported automatically.

Here is a copy and paste from the report page.

chromium@387905,v8@a0d2f240c3187.6 0.547723 5 good
chromium@387905,v8@139617b0d5185.4 0.547723 5 bad

Assign to mstarzinger@ who landed 139617b0d5185, but we may need another v8 bisect to find more accurate revision?

CC: prasadv@ as a today's bot sheriff to triage the issue that result wasn't reported, also could help to run another v8 bisect?

IIUC, then there are 24 CLs in the regression range mentioned in comment #4.

https://chromium.googlesource.com/v8/v8/+log/a0d2f240c3..139617b0d5

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Perf sheriff ping

Looking at the results from a wider time range, this appears likely to have been noise.