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

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


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

android-one

=== Auto-CCing suspected CL author scottmg@chromium.org ===

Hi scottmg@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : Turn on assert_no_deps for blink in browser
Author  : scottmg
Commit description:
  
R=brettw@chromium.org
BUG= 582206 

Review-Url: https://codereview.chromium.org/1926443002
Cr-Commit-Position: refs/heads/master@{#390123}
Commit  : ffb95be04fb4effb750884083cb1c166c5499b7a
Date    : Wed Apr 27 18:05:14 2016


===== TESTED REVISIONS =====
Revision         Mean       Std Dev      N  Good?
chromium@390087  0.0604217  0.000226058  5  good
chromium@390108  0.0607515  0.000159184  5  good
chromium@390119  0.0599416  0.000464867  5  good
chromium@390122  0.0601607  0.000182736  5  good
chromium@390123  0.0540433  0.000174236  5  bad    <--
chromium@390124  0.05406    0.000275185  5  bad
chromium@390129  0.0541687  0.000161585  5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 607639

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.events
Test Metric: hit-test-lots-of-layers/hit-test-lots-of-layers
Relative Change: 10.35%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1288
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9014113217096923040


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

| 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 don't think that's possible, it's a build-time only debug check.

Looks like this got fixed and subsequently regressed again.  I'll try another bisect, but it's probably safe to close this.

Closing given that the graph has recovered subsequently (see attached image).

Deleted: Screen Shot 2016-05-19 at 2.57.51 PM.png 107 KB

	Screen Shot 2016-05-19 at 2.57.51 PM.png 107 KB View Download