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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg7OD6oQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgrMOa8AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg7MC8qAsM


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

android-nexus6

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

Hi cco3@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 : Record Physical Web status at Chrome startup
Author  : cco3
Commit description:
  
BUG= 594194 

Review-Url: https://codereview.chromium.org/2006363002
Cr-Commit-Position: refs/heads/master@{#396008}
Commit  : c8aece4cc68d2088887c01911f930292393bcddb
Date    : Wed May 25 22:29:00 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@395985  24597.4  72.5038  5  good
chromium@396007  24594.4  62.0548  5  good
chromium@396008  24987.4  42.665   5  bad    <--
chromium@396009  25000.2  63.6647  5  bad
chromium@396010  24982.0  77.9583  5  bad
chromium@396013  24966.4  60.5747  5  bad
chromium@396018  24961.6  78.3633  5  bad
chromium@396029  24929.8  45.6257  5  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 615190

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests storage.indexeddb_endure
Test Metric: vm_private_dirty_final_browser/vm_private_dirty_final_browser
Relative Change: 1.35%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2202
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9011568452143165984


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

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

It's probably related...I'll revert.

The logs state that these tests took 3 hours to run...I'm trying to run this locally, is there any way I can narrow down the set of tasks that need to be run?

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d3f4c2c39b8656efb783b914044fcfd181b93756

commit d3f4c2c39b8656efb783b914044fcfd181b93756
Author: cco3 <cco3@chromium.org>
Date: Fri May 27 19:20:34 2016

Revert "Record Physical Web status at Chrome startup"

This reverts commit c8aece4cc68d2088887c01911f930292393bcddb.

BUG= 615190 

Review-Url: https://codereview.chromium.org/2016153002
Cr-Commit-Position: refs/heads/master@{#396531}

[modify] https://crrev.com/d3f4c2c39b8656efb783b914044fcfd181b93756/chrome/android/java/src/org/chromium/chrome/browser/physicalweb/PhysicalWeb.java
[modify] https://crrev.com/d3f4c2c39b8656efb783b914044fcfd181b93756/chrome/android/java/src/org/chromium/chrome/browser/physicalweb/PhysicalWebUma.java

This did recover with the revert.