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

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


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

android-nexus9

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

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@419583  320.813  10.9029  18  good
chromium@419849  318.257  24.3888  17  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 649987

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.layout
Test Metric: flexbox-row-wrap/flexbox-row-wrap
Relative Change: 0.81%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2124
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000579544813611728


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

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

cbiesinger: your change looks like the only one in the revision range that might have affected layout, and the graph looks like it might be a real regression regardless of what bisect says.
https://codereview.chromium.org/2346403002

Perf sheriff ping

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

That patch did not affect layout without a special flag on, it can't have caused this regression. I started another bisect job in case that's helpful...

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@419583  318.269  24.8093  18  good
chromium@419849  323.113  16.1445  21  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 649987

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.layout
Test Metric: flexbox-row-wrap/flexbox-row-wrap
Relative Change: 5.69%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2183
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999066892887031104


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

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

The regression has gone away. I think we can close this.