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

commit cd86bbdcc222fce682c59eb2a5ed1c694f0a4f5b
Author: simonhatch <simonhatch@chromium.org>
Date: Wed Aug 03 21:55:59 2016

Disable dromaeo.jslibattrjquery on Android One.

TBR=nednguyen@google.com
BUG= 634055 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;

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

[modify] https://crrev.com/cd86bbdcc222fce682c59eb2a5ed1c694f0a4f5b/tools/perf/benchmarks/dromaeo.py

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

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


===== TESTED REVISIONS =====
Revision         Exit Code  Std Dev  N  Good?
chromium@408999  0          N/A      5  good
chromium@409050  0          N/A      5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 634055

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1478
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005250388803498576


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

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

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


===== TESTED REVISIONS =====
Revision         Exit Code  Std Dev  N  Good?
chromium@408943  0          N/A      5  good
chromium@409146  0          N/A      5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 634055

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1479
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005244501007966992


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

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

haraken can you look into this? The bisect bots don't seem to be able to reproduce this unfortunately.

It's hard to diagnose this issue without having a stack trace. Is there any way to get the stack trace?

Edited description to include a link to failure: https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf%20%282%29/builds/3704

I'm not sure there is a stack trace, looking at the log it looks like the test either didn't run or didn't produce any results?

sheriff ping!

This benchmark probably shoulnd't have been disabled. That error means the benchmark did not run at all, likely because of infra issues. Since then, that will now turn the step purple instead of red so this wont be an issue going forward.

https://codereview.chromium.org/2787263004/

This benchmark has been deleted.