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

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


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

android-galaxy-s5

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/989
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/997
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/998
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

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

This CL is suspicious. Assigning to author.

https://chromium.googlesource.com/chromium/src/+/9ee7a4109cbc763067538c360c36ff2e1ba3ee13

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/1083
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

Any updates? dimich - could this be your CL that regressed this benchmark?

As I understand it, the failed test is compositor perftest, specifically having nothing to do with a page load. I don't see how my CL could potentially affect the compositor serialization code which seems to be testing the speed of serializing IPC messages for compositor.

Some changes in generic IPC or in cc/ folder could probably be more responsible.

This bot has been decommissioned.

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

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