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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg97zlqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgt8mLrgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgt5uyoQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgt_mAoQoM


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

chromium-rel-win7-gpu-intel
win-zenbook

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

===== 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@421695  0.852373  0.393477  21  good
chromium@421773  0.918295  0.327338  21  bad

Bisect job ran on: android_webview_arm64_aosp_perf_bisect
Bug ID: 673653

Test Command: src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.flipboard v8.browsing_desktop
Test Metric: v8-gc-incremental-step_avg/browse_news/browse_news_flipboard
Relative Change: 7.73%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_webview_arm64_aosp_perf_bisect/builds/599
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993407139144077152


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

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

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