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

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


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

android-nexus5X

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev     N   Good?
chromium@409158  16.6257  0.018156    18  good
chromium@409184  16.6067  0.00733739  9   bad
chromium@409210  16.6128  0.00903811  18  bad
chromium@409261  16.6096  0.0105746   12  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 633888

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests scheduler.tough_scheduling_cases
Test Metric: mean_frame_time/mean_frame_time
Relative Change: 0.13%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/425
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005365538790204992


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

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev     N   Good?
chromium@409158  16.6257  0.018156    18  good
chromium@409184  16.6067  0.00733739  9   bad
chromium@409210  16.6128  0.00903811  18  bad
chromium@409261  16.6096  0.0105746   12  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 633888

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests scheduler.tough_scheduling_cases
Test Metric: mean_frame_time/mean_frame_time
Relative Change: 0.13%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/425
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005365538790204992


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

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

Looking bisect logs, https://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/425

In the step 34, we are failing at 'gsutil download_build_product' step.

https://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/434/steps/gsutil%20download_build_product/logs/stdio

CommandException: No URLs matched: gs://chrome-perf-tryjob/android_perf_rel/full-build-linux_964382baf9939830e6c0d2ca391595f8dcf3e55a_aa4d30ea-13d0-4c7b-b827-9c10f61903a1.zip
WARNING:root:Command /usr/bin/python -u /b/build/scripts/slave/.recipe_deps/depot_tools/gsutil.py --force-version 4.7 -- cp gs://chrome-perf-tryjob/android_perf_rel/full-build-linux_964382baf9939830e6c0d2ca391595f8dcf3e55a_aa4d30ea-13d0-4c7b-b827-9c10f61903a1.zip /b/build/slave/android_nexus5X_perf_bisect/build/src/out/build_product.zip failed with retcode 1, try 1.1.
CommandException: No URLs matched: gs://chrome-perf-tryjob/android_perf_rel/full-build-linux_964382baf9939830e6c0d2ca391595f8dcf3e55a_aa4d30ea-13d0-4c7b-b827-9c10f61903a1.zip
WARNING:root:Command /usr/bin/python -u /b/build/scripts/slave/.recipe_deps/depot_tools/gsutil.py --force-version 4.7 -- cp gs://chrome-perf-tryjob/android_perf_rel/full-build-linux_964382baf9939830e6c0d2ca391595f8dcf3e55a_aa4d30ea-13d0-4c7b-b827-9c10f61903a1.zip /b/build/slave/android_nexus5X_perf_bisect/build/src/out/build_product.zip failed with retcode 1, try 1.2.
WARNING:root:Trying harder: deleting tracker files
CommandException: No URLs matched: gs://chrome-perf-tryjob/android_perf_rel/full-build-linux_964382baf9939830e6c0d2ca391595f8dcf3e55a_aa4d30ea-13d0-4c7b-b827-9c10f61903a1.zip
WARNING:root:Command /usr/bin/python -u /b/build/scripts/slave/.recipe_deps/depot_tools/gsutil.py --force-version 4.7 -- cp gs://chrome-perf-tryjob/android_perf_rel/full-build-linux_964382baf9939830e6c0d2ca391595f8dcf3e55a_aa4d30ea-13d0-4c7b-b827-9c10f61903a1.zip /b/build/slave/android_nexus5X_perf_bisect/build/src/out/build_product.zip failed with retcode 1, try 2.1.
CommandException: No URLs matched: gs://chrome-perf-tryjob/android_perf_rel/full-build-linux_964382baf9939830e6c0d2ca391595f8dcf3e55a_aa4d30ea-13d0-4c7b-b827-9c10f61903a1.zip
WARNING:root:Command /usr/bin/python -u /b/build/scripts/slave/.recipe_deps/depot_tools/gsutil.py --force-version 4.7 -- cp gs://chrome-perf-tryjob/android_perf_rel/full-build-linux_964382baf9939830e6c0d2ca391595f8dcf3e55a_aa4d30ea-13d0-4c7b-b827-9c10f61903a1.zip /b/build/slave/android_nexus5X_perf_bisect/build/src/out/build_product.zip failed with retcode 1, try 2.2.
WARNING:root:Trying harder: deleting tracker files
ERROR:root:Command /b/build/scripts/slave/.recipe_deps/depot_tools/gsutil.py --force-version 4.7 -- cp gs://chrome-perf-tryjob/android_perf_rel/full-build-linux_964382baf9939830e6c0d2ca391595f8dcf3e55a_aa4d30ea-13d0-4c7b-b827-9c10f61903a1.zip /b/build/slave/android_nexus5X_perf_bisect/build/src/out/build_product.zip failed 4 retries, giving up.
step returned non-zero exit code: 1

Is this infra issue?

Let me assigned prasadv@, today's Perfbot Sheriff.

Note: only one bisect log exists at https://chromeperf.appspot.com/group_report?bug_id=633888
But, we are seeing two reports at #2-#3, #4-#5. I'm not sure why.

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

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev     N   Good?
chromium@409158  16.5545  0.00805923  12  good
chromium@409261  16.5512  0.00845044  18  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 633888

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests scheduler.tough_scheduling_cases
Test Metric: mean_frame_time/mean_frame_time
Relative Change: 0.02%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/433
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005365538790204992


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

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

Perf sheriff ping: reminder to follow up on possible performance issues

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

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N   Good?
chromium@409158  16.6735  0.0230177  15  good
chromium@409261  16.665   0.0185677  18  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 633888

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests scheduler.tough_scheduling_cases
Test Metric: mean_frame_time/mean_frame_time
Relative Change: 0.00%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/692
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000698962733602848


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

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

1%, four bisects run without finding a big enough regression, wontfix.