Jetstream failing on android one perf bot |
||||
Issue descriptionhttps://luci-milo.appspot.com/buildbot/chromium.perf/Android%20Nexus5%20Perf%20%283%29/ Traceback (most recent call last): File "/b/c/b/Android_Nexus5_Perf__3_/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 88, in _RunStoryAndProcessErrorIfNeeded state.RunStory(results) File "/b/c/b/Android_Nexus5_Perf__3_/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function return func(*args, **kwargs) File "/b/c/b/Android_Nexus5_Perf__3_/src/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 302, in RunStory self._current_page, self._current_tab, results) File "/b/c/b/Android_Nexus5_Perf__3_/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function return func(*args, **kwargs) File "/b/c/b/Android_Nexus5_Perf__3_/src/tools/perf/benchmarks/jetstream.py", line 59, in ValidateAndMeasurePage """, timeout=600) File "/b/c/b/Android_Nexus5_Perf__3_/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function return func(*args, **kwargs) File "/b/c/b/Android_Nexus5_Perf__3_/src/third_party/catapult/telemetry/telemetry/internal/browser/web_contents.py", line 191, in WaitForJavaScriptCondition return self._inspector_backend.WaitForJavaScriptCondition(*args, **kwargs) File "/b/c/b/Android_Nexus5_Perf__3_/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function return func(*args, **kwargs) File "/b/c/b/Android_Nexus5_Perf__3_/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py", line 294, in WaitForJavaScriptCondition e.message + '\n' + debug_message) TimeoutException: Timed out while waiting 600s for IsJavaScriptExpressionTrue.
,
May 2 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : jetstream Metric : 3d-cube/http___browserbench.org_JetStream_ Revision Exit Code N chromium@467818 1 +- N/A 2 good chromium@467981 1 +- N/A 2 bad 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 --story-filter=http...browserbench.org.JetStream. jetstream Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980777362025056896 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6651606830940160 | 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!
,
May 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980692171194578848
,
May 2 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: android_one_perf_bisect Benchmark : jetstream Metric : benchmark_duration/benchmark_duration Revision Exit Code N chromium@467921 1 +- N/A 3 good chromium@467968 1 +- N/A 3 bad 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 jetstream Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980692171194578848 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6392184632246272 | 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!
,
May 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980685840961454944
,
May 2 2017
=== BISECT JOB RESULTS === NO Test failure found Bisect Details Configuration: android_one_perf_bisect Benchmark : jetstream Metric : benchmark_duration/benchmark_duration Revision Exit Code N chromium@467800 1 +- N/A 3 good chromium@467968 1 +- N/A 3 bad 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 jetstream Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980685840961454944 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4939466570989568 | 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!
,
May 2 2017
Looking at the screenshot from the device, it looks like the jetstream benchmark isn't finished running: https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/profiler-file-id_0-2017-05-02_07-49-4287534.png We can either disable the test on svelte devices or we can look into increasing the timeout. I'm not sure how important this benchmark is to run on svelte android devices. To increase the timeout we would just increase it here: https://cs.chromium.org/chromium/src/tools/perf/benchmarks/jetstream.py?q=tools/perf/benchmarks/jets+package:%5Echromium$&l=59
,
May 2 2017
Also, it stopped failing on n5, but is still failing on a1 devices.
,
May 2 2017
Actually it passed once on the n5 and failed again after that. CL to increase timeout here: https://codereview.chromium.org/2860433003/
,
May 2 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ba2e08f19f4a5967a1eb9c06edc7938c89144063 commit ba2e08f19f4a5967a1eb9c06edc7938c89144063 Author: rnephew <rnephew@chromium.org> Date: Tue May 02 23:38:45 2017 [Telemetry] Increase timeout on jetstream benchmark. It is timing out on n5 and A1 android devices. BUG= 717100 Review-Url: https://codereview.chromium.org/2860433003 Cr-Commit-Position: refs/heads/master@{#468820} [modify] https://crrev.com/ba2e08f19f4a5967a1eb9c06edc7938c89144063/tools/perf/benchmarks/jetstream.py
,
May 3 2017
Last 3 runs on both bots have passed. Closing. |
||||
►
Sign in to add a comment |
||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, May 1 2017