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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4MOSiQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4MOS8QsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgoLuNmQoM


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

linux-release

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8989906774220002272

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6989
Failure reason: the build has failed due to infrastructure failure.

The last data point prior to the regression was from 2014, I really don't think this can be resolved.

Yeah, probably not ;)

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982651801517292208

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/7167
Failure reason: the build has failed.
Additional errors:
The revision range could not be expanded, or the commit positions could not be resolved into commit hashes.