Bisect started at https://chromeperf.appspot.com/buildbucket_job_status/9015644126933097472

===== BISECT JOB RESULTS =====
Status: completed


===== TESTED REVISIONS =====
Revision                Exit Code   Std. Dev.   Num Values  Good?
chromium@384315         1           N/A         5           good
chromium@384341         1           N/A         5           bad

Bisect job ran on: linux_perf_bisect
Bug ID: 602439

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --also-run-disabled-tests rasterize_and_record_micro.top_25_smooth
Test Metric: pixels_recorded/Blogger
Relative Change: 0.00%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6394
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9015644126933097472


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=602439

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

I thought that the range specified would be sufficient to detect the regression, but it looks like it wasn't. I started a bisect on a broader range here: https://chromiumcodereview-hr.appspot.com/1883533005

Bisect finished. 

https://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6397/steps/Results/logs/stdio

===== SUSPECTED CL(s) =====
Subject : Adapt and reland old position sticky implementation from https://codereview.chromium.org/346603007
Author  : flackr@chromium.org
Link    : https://chromium.googlesource.com/chromium/src/+/846f623cb1ef78d90e620c2a7a6557544a86b692
Commit  : 846f623cb1ef78d90e620c2a7a6557544a86b692
Date    : Thu, 31 Mar 2016 09:31:11 +0000

Unassigning this from flackr@ - his CL was already reverted, and was not the CL we were looking for.

Bisect with only 1 repeat count:
https://chromeperf.appspot.com/buildbucket_job_status/9015554466525764448

Is the regression range correct? As far as I can tell, this has been failing since build 14369, which gives it a regression range of 384233:384244. That also makes it a duplicate of  issue 600377 , but comments on that bug are unclear as to whether there were more/different failures since then.

Tip: use Firefighter to go digging around in history past the last 200 builds.
https://chromiumperfstats.appspot.com/?master=chromium.perf&os=linux&benchmark=rasterize_and_record_micro.top_25_smooth&start_time=3w