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

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


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

linux-release

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean       Std Dev   N    Good?
chromium@431895  0.0476333  0.368225  120  good
chromium@431947  0.050225   0.475597  120  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 666020

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests rasterize_and_record_micro.top_25
Test Metric: record_time/record_time
Relative Change: None

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


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

| 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!

Mm, bisect, I'm pretty sure you're wrong. Try again?
If it fails again, then let's ping the metric owner and Mr.s Bisect, robertocn and dtu.

Relatedly, this metric regressed even more a while ago and that regression was never resolved: https://bugs.chromium.org/p/chromium/issues/detail?id=665331

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean       Std Dev   N    Good?
chromium@431895  0.0478167  0.372679  120  good
chromium@431947  0.0502083  0.471849  120  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 666020

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests rasterize_and_record_micro.top_25
Test Metric: record_time/record_time
Relative Change: None

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


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

| 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!

vmpstr: please take a look at above linked graphs. I reported the bad bisect so maybe we will be able to fix those and try again, but can you take a look in the meantime?

wangxianzhu: The graph gets better with the land of https://codereview.chromium.org/2430313004 and regresses with its revert. Doesn't reproduce in bisect. Up to you whether we should keep this open.

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

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : rasterize_and_record_micro.top_25
  Metric       : record_time/record_time

Revision             Result                     N
chromium@431895      0.0478167 +- 0.372679      120      good
chromium@431947      0.0502083 +- 0.471849      120      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests rasterize_and_record_micro.top_25

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982632445676268784

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5254636691259392


| 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 Speed>Bisection.  Thank you!

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : rasterize_and_record_micro.top_25
  Metric       : record_time/record_time

Revision             Result                     N
chromium@431895      0.0476333 +- 0.368225      120      good
chromium@431947      0.050225 +- 0.475597       120      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests rasterize_and_record_micro.top_25

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982624467695593904

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5283294726324224


| 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 Speed>Bisection.  Thank you!