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

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


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

android-galaxy-s5

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

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

Hi xiyuan@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 : kiosk: Add status report for os update and running app
Author  : xiyuan
Commit description:
  
- Update chrome_device_settings.proto to include report setting
  for os_update_status and running_kiosk_app;
- Update device_management_backend.proto to include os_update_status
  and running_kiosk_app in DeviceStatusReportRequest;

BUG= 577800 
TEST=browser_tests --gtest_filter=DeviceStatusCollectorTest.*OsUpdateStatus*:
    DeviceStatusCollectorTest.*RunningKioskApp*

Review-Url: https://codereview.chromium.org/2132663002
Cr-Commit-Position: refs/heads/master@{#405196}
Commit  : bdf91bc327487db842a0831fbf2247b671b3d988
Date    : Wed Jul 13 16:59:44 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@405191  3394.35  37.3159  12  good
chromium@405195  3411.03  30.5861  12  good
chromium@405196  3526.42  81.2122  5   bad    <--
chromium@405197  3475.26  28.5986  8   bad
chromium@405199  3470.03  51.4285  8   bad
chromium@405206  3495.54  31.0577  5   bad
chromium@405220  3477.35  43.2854  5   bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 628118

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests speedometer
Test Metric: jQuery-TodoMVC/jQuery-TodoMVC
Relative Change: 2.83%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/792
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007175531912854832


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

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

Think it should be something else. My CL is a chromeos only change and should only kick in on an enterprise enrolled device. Not sure how it could affect Android.

Only one alert, graph looks noisy. Closing.