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

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


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

android-nexus7v2

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : meade
  Commit : 3a001533b29c0fe28f2354285b2c2ac8d57d8ce6
  Date   : Mon Mar 13 05:26:20 2017
  Subject: Un-DCHECK-guard ThreadRestrictionVerifier for strings.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : blink_perf.css
  Metric       : AttributeDescendantSelector/AttributeDescendantSelector
  Change       : 22.54% | 35.9437161832 -> 27.8421295971

Revision             Result                   N
chromium@456315      35.9437 +- 0.702749      6      good
chromium@456319      34.9399 +- 0.834378      6      good
chromium@456321      33.868 +- 1.3274         6      good
chromium@456322      35.6812 +- 0.671335      6      good
chromium@456323      27.3385 +- 0.476211      6      bad       <--
chromium@456331      27.8421 +- 0.934455      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.css

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

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


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