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

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


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

linux-perf

rasterize_and_record_micro.top_25 - Benchmark documentation link:
  None

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/159ee39a940000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/159ee39a940000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14c2ab57940000

There was a regression (to our bad value), then a progression (better than the baseline) then another regression (to the same bad value). So it looks kinda like reverts or something but the progression is interesting. I've started some bisects of each regression point.

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14c2ab57940000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/178aa86a540000

This test seems to jump between a low and high value every so often, where the higher value is a 300% regression. This means a lot of false alerts but also anything real will be hidden in that noise.

Deleted: 300.png 58.9 KB

	300.png 58.9 KB View Download

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/178aa86a540000