media.android.tough_video_cases_tbmv2 failing on Android Nexus5 Perf bot |
|||
Issue descriptionFailure.... AdbShellCommandFailedError: (device: 03848cee0ae584a5) shell command run via adb failed on the device: command: printf "%s " /proc/[0-9]*/task/[0-9]* exit status: 127 output: - /system/bin/sh: printf: not found Will try to bisect, but looks like a catapult change is causing this failure.
,
Mar 31 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983584517420253216
,
Mar 31 2017
,
Mar 31 2017
Sorry about this. John is planning on disabling it I think.
,
Mar 31 2017
This will be fixed by https://codereview.chromium.org/2790493008/
,
Apr 1 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/6c053334d79f15e04910119bd174d45fbf5fd613 commit 6c053334d79f15e04910119bd174d45fbf5fd613 Author: johnchen <johnchen@chromium.org> Date: Sat Apr 01 01:25:39 2017 Disable media.android.tvc_tbmv2 on most devices The media.andoid.tough_video_cases_tmbv2 benchmark is failing on devices other than Nexus 5X. Disabling on those devices until the root cause can be found. BUG= 707286 Review-Url: https://codereview.chromium.org/2790493008 Cr-Commit-Position: refs/heads/master@{#461298} [modify] https://crrev.com/6c053334d79f15e04910119bd174d45fbf5fd613/tools/perf/benchmarks/media.py
,
Apr 1 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : media.android.tough_video_cases_tbmv2 Metric : BenchmarkDuration/BenchmarkDuration To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests media.android.tough_video_cases_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983584517420253216 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5596362042769408 | 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!
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982611856815307664
,
Apr 11 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : media.android.tough_video_cases_tbmv2 Metric : BenchmarkDuration/BenchmarkDuration To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests media.android.tough_video_cases_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982611856815307664 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5596362042769408 | 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!
,
Apr 12 2017
,
Apr 12 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/97a6fea550e9d2fcd81649cffbb0de8b4750af9a commit 97a6fea550e9d2fcd81649cffbb0de8b4750af9a Author: johnchen <johnchen@chromium.org> Date: Wed Apr 12 23:49:54 2017 Disable atrace in TBMv2 media benchmarks Remove enable_atrace_trace option in TBMv2 based media benchmarks, as it is causing errors on some Android devices (due to bug 710920 ). BUG= 707286 , 710920 Review-Url: https://codereview.chromium.org/2796623003 Cr-Commit-Position: refs/heads/master@{#464210} [modify] https://crrev.com/97a6fea550e9d2fcd81649cffbb0de8b4750af9a/tools/perf/benchmarks/media.py |
|||
►
Sign in to add a comment |
|||
Comment 1 by mikec...@chromium.org
, Mar 31 2017