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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxdr7sgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxYnWvQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxZDVuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxc75rAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxZDwvQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgheG6_goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxa3JrwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghbe05ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxcTTsQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgheSk-QsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxe2ltQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghY-UsgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxe2zrAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghdeW_QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghenZtAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxZ7svAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxfz6qwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxYrI-AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxfiV-AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxZCftwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxdDivwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxdD2oQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghdHl7gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxZ7VqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxfjQ_woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxZChqgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghff8uAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpZCNqQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxbCBvAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxbDlowoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxd3KoQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxbjppgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxZSbtAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghbeT4QkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxdrtowkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxYnWvQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxebwugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxajj-AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxf6JtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxffCqwkM


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

android-galaxy-s5
android-nexus5
android-nexus6
android-nexus7v2

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4149
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/8999843409342109008

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2593
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.

Anybody know what to do about this failing bisect?

Step('Gathering reference values.Recipe failed. Reason: Testing the "good" revision failed') failed with return_code 1

See this graph instead of the group_report
https://chromeperf.appspot.com/report?sid=94b0b299f7eb80120cd10383205a26e9dc007e1cf037746f803d7de2690be59b

(Why doesn't the group_report work?

The logs in the bisect from #5 look like a problem with the APK? Roberto, can you take a look?


step returned non-zero exit code: 1
@@@STEP_LOG_LINE@Failure Output@[Running on builder: "android_nexus6_perf_bisect"]@@@
@@@STEP_LOG_LINE@Failure Output@DBUS_SESSION_BUS_ADDRESS env var not found, starting dbus-launch@@@
@@@STEP_LOG_LINE@Failure Output@ setting DBUS_SESSION_BUS_ADDRESS to unix:abstract=/tmp/dbus-bDFh8OFQW3,guid=7e03d87f084f68c71680ab2057f20392@@@
@@@STEP_LOG_LINE@Failure Output@ setting DBUS_SESSION_BUS_PID to 32511@@@
@@@STEP_LOG_LINE@Failure Output@Window manager (openbox) started.@@@
@@@STEP_LOG_LINE@Failure Output@Additional test environment:@@@
@@@STEP_LOG_LINE@Failure Output@  CHROME_DEVEL_SANDBOX=/opt/chromium/chrome_sandbox@@@
@@@STEP_LOG_LINE@Failure Output@  CHROMIUM_OUTPUT_DIR=/b/rr/tmpb1AJnB/w/src/out/Release@@@
@@@STEP_LOG_LINE@Failure Output@  LD_LIBRARY_PATH=/b/rr/tmpb1AJnB/w/src/out/Release:/b/rr/tmpb1AJnB/w/src/out/Release/lib:/b/rr/tmpb1AJnB/w/src/out/Release/lib.target@@@
@@@STEP_LOG_LINE@Failure Output@@@@
@@@STEP_LOG_LINE@Failure Output@/usr/bin/python /b/c/b/android_nexus6_perf_bisect/src/build/android/test_runner.py gtest --release -s cc_perftests --verbose@@@
@@@STEP_LOG_LINE@Failure Output@I    0.002s Main  command: /b/c/b/android_nexus6_perf_bisect/src/build/android/test_runner.py gtest --release -s cc_perftests --verbose@@@
@@@STEP_LOG_LINE@Failure Output@C    0.003s Main  Could not find apk or executable for cc_perftests@@@
@@@STEP_LOG_LINE@Failure Output@E    0.003s Main  Unrecognized error occurred.@@@
@@@STEP_LOG_LINE@Failure Output@Traceback (most recent call last):@@@
@@@STEP_LOG_LINE@Failure Output@  File "/b/c/b/android_nexus6_perf_bisect/src/build/android/test_runner.py", line 946, in main@@@
@@@STEP_LOG_LINE@Failure Output@    return RunTestsCommand(args)@@@
@@@STEP_LOG_LINE@Failure Output@  File "/b/c/b/android_nexus6_perf_bisect/src/build/android/test_runner.py", line 766, in RunTestsCommand@@@
@@@STEP_LOG_LINE@Failure Output@    return RunTestsInPlatformMode(args)@@@
@@@STEP_LOG_LINE@Failure Output@  File "/b/c/b/android_nexus6_perf_bisect/src/build/android/test_runner.py", line 812, in RunTestsInPlatformMode@@@
@@@STEP_LOG_LINE@Failure Output@    with test_instance_factory.CreateTestInstance(args, infra_error) as test:@@@
@@@STEP_LOG_LINE@Failure Output@  File "/b/c/b/android_nexus6_perf_bisect/src/build/android/pylib/base/test_instance_factory.py", line 16, in CreateTestInstance@@@
@@@STEP_LOG_LINE@Failure Output@    args, isolator.Isolator(), error_func)@@@
@@@STEP_LOG_LINE@Failure Output@  File "/b/c/b/android_nexus6_perf_bisect/src/build/android/pylib/gtest/gtest_test_instance.py", line 219, in __init__@@@
@@@STEP_LOG_LINE@Failure Output@    error_func('Could not find apk or executable for %s' % self._suite)@@@
@@@STEP_LOG_LINE@Failure Output@  File "/b/c/b/android_nexus6_perf_bisect/src/build/android/test_runner.py", line 806, in infra_error@@@
@@@STEP_LOG_LINE@Failure Output@    sys.exit(constants.INFRA_EXIT_CODE)@@@
@@@STEP_LOG_LINE@Failure Output@SystemExit: 87@@@
@@@STEP_LOG_LINE@Failure Output@<Thread(Thread-1, started 140394520479488)> ProcessRead: proc.stdout finished.@@@
@@@STEP_LOG_LINE@Failure Output@<Thread(Thread-1, started 140394520479488)> ProcessRead: cleaning up.@@@
@@@STEP_LOG_LINE@Failure Output@<Thread(Thread-2, started daemon 140394512086784)> TimedFlush: Finished@@@
@@@STEP_LOG_LINE@Failure Output@<Thread(Thread-1, started 140394520479488)> ProcessRead: finished.@@@
@@@STEP_LOG_LINE@Failure Output@Stopping Xvfb with pid 32513 ...@@@
@@@STEP_LOG_LINE@Failure Output@Xvfb pid file removed@@@
@@@STEP_LOG_LINE@Failure Output@ killed dbus-daemon with PID 32511@@@
@@@STEP_LOG_LINE@Failure Output@ cleared DBUS_SESSION_BUS_ADDRESS environment variable@@@
@@@STEP_LOG_END@Failure Output@@@
@@@STEP_LOG_LINE@stderr@2 new files were left in /tmp: Fix the tests to clean up themselves.@@@
@@@STEP_LOG_END@stderr@@@
@@@STEP_FAILURE@@@

robertocn@ : Ping!

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2695
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/8995785780880740576

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Step('Compare samples') failed with return_code 1
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@420384  N/A   N/A      0  good
chromium@420422  N/A   N/A      0  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 650022

Test Command: src/build/android/test_runner.py gtest --release -s cc_perftests --verbose
Test Metric: build_task_graph_task_graph_runner/0_32_0
Relative Change: None

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


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

| 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/8993179133833866208

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: No values were found while testing the reference range.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@420384  N/A   N/A      0  good
chromium@420426  N/A   N/A      0  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 650022

Test Command: src/build/android/test_runner.py gtest --release -s cc_perftests --verbose
Test Metric: schedule_tasks_task_graph_runner/0_32_0
Relative Change: 0.00%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3555
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993179133833866208


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

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

These will all be invalid as they are specific to Samsung S5s, which we do not trust to give us a signal and have subsequently removed from the waterfalls. If you think this regression is real, please re-open.

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4866
Failure reason: the build has failed due to infrastructure failure.

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

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : cc_perftests
  Metric       : schedule_tasks_task_graph_runner/0_32_0


To Run This Test
  src/build/android/test_runner.py gtest --release -s cc_perftests --verbose

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982584603478340272

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5790377364160512


| 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 Speed>Bisection.  Thank you!