Issue metadata
Sign in to add a comment
|
smoothness.tough_filters_cases failure on chromium.perf on Android One Perf (1) |
||||||||||||||||||||
Issue descriptionRevision range first seen: Looks like it roughly started happening around Feb 28 Link to failing step log: https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf%20%281%29/builds/1787
,
Mar 7 2016
I'm hoping some infra folks can make sense of that Telemetry stack trace and take it on? I'm at a loss.
,
Mar 7 2016
re #3: Added you as listed owner of test. Also, I have a bisect out that at least so far, seems to be reproducing a failure.
,
Mar 7 2016
===== BISECT JOB RESULTS ===== Status: completed === Bisection aborted === The bisect was aborted because The metric values for the initial "good" and "bad" revisions match the expected direction of improvement. Thus, likely represent an improvement and not a 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: * The initial regression range for return code appears to show NO sign of a regression. ===== TESTED REVISIONS ===== Revision Exit Code Std. Dev. Num Values Good? chromium@378146 1 N/A 5 good chromium@378171 1 N/A 5 bad Bisect job ran on: android_one_perf_bisect Bug ID: 592675 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests smoothness.tough_filters_cases Test Metric: Filter-queueing_durations/Filter-queueing_durations Relative Change: 0.00% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1192 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9018824089630813040 | 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 label Cr-Tests-AutoBisect. Thank you!
,
Mar 7 2016
Trying again: https://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1193 Had failures on both the earlier and later revisions on last run.
,
Mar 8 2016
===== BISECT JOB RESULTS ===== Status: completed ===== TESTED REVISIONS ===== Revision Exit Code Std. Dev. Num Values Good? chromium@376673 0 N/A 5 good chromium@376860 0 N/A 5 good chromium@376884 0 N/A 5 good chromium@376896 0 N/A 5 good chromium@376899 0 N/A 5 good chromium@376900 1 N/A 5 bad chromium@376901 1 N/A 5 bad chromium@376902 1 N/A 5 bad chromium@376907 1 N/A 5 bad chromium@376953 1 N/A 5 bad chromium@377046 1 N/A 5 bad chromium@377419 1 N/A 5 bad chromium@378165 1 N/A 5 bad Bisect job ran on: android_one_perf_bisect Bug ID: 592675 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests smoothness.tough_filters_cases Test Metric: Filter-frame_times/Filter-frame_times Relative Change: Zero to non-zero Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1194 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9018814961281405600 | 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 label Cr-Tests-AutoBisect. Thank you!
,
Mar 10 2016
Not sure why but this seems to have cleared up and the bot is green now. The bisect in #7 points to a skia roll. Can probably close this, but I sent out another bisect, out of curiosity. https://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1199
,
Mar 10 2016
===== BISECT JOB RESULTS ===== Status: completed === Bisection aborted === The bisect was aborted because The metric values for the initial "good" and "bad" revisions match the expected direction of improvement. Thus, likely represent an improvement and not a 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: * The initial regression range for return code appears to show NO sign of a regression. ===== TESTED REVISIONS ===== Revision Exit Code Std. Dev. Num Values Good? chromium@379854 1 N/A 5 good chromium@379935 0 N/A 5 bad Bisect job ran on: android_one_perf_bisect Bug ID: 592675 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests smoothness.tough_filters_cases Test Metric: frame_times/frame_times Relative Change: 100.00% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1199 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9018552184825030544 | 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 label Cr-Tests-AutoBisect. Thank you!
,
Mar 10 2016
Filed bug 593865 on the bisect failure in #9 |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by simonhatch@chromium.org
, Mar 7 2016Snippet from log: (INFO) 2016-03-07 09:54:44,979 cmd_helper._ValidateAndLogCommand:153 [host]> /b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s AG8604420GI4IGC shell '( logcat -d -t 500 );echo %$?' Traceback (most recent call last): File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/android_platform/development/scripts/stack", line 258, in <module> sys.exit(main(sys.argv[1:])) File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/android_platform/development/scripts/stack", line 194, in main constants.CheckOutputDirectory() File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/android_platform/development/scripts/../../../../build/android/pylib/constants/__init__.py", line 264, in CheckOutputDirectory raise Exception('Neither CHROMIUM_OUTPUT_DIR nor CHROMIUM_OUT_DIR ' Exception: Neither CHROMIUM_OUTPUT_DIR nor CHROMIUM_OUT_DIR has been set Traceback (most recent call last): File "/b/build/slave/Android_One_Perf__1_/build/src/build/android/tombstones.py", line 273, in <module> sys.exit(main()) File "/b/build/slave/Android_One_Perf__1_/build/src/build/android/tombstones.py", line 255, in main constants.CheckOutputDirectory() File "/b/build/slave/Android_One_Perf__1_/build/src/build/android/pylib/constants/__init__.py", line 264, in CheckOutputDirectory raise Exception('Neither CHROMIUM_OUTPUT_DIR nor CHROMIUM_OUT_DIR ' Exception: Neither CHROMIUM_OUTPUT_DIR nor CHROMIUM_OUT_DIR has been set (ERROR) 2016-03-07 09:54:45,173 exceptions.__init__:69 Problem when trying to gather standard output: 'NoneType' object has no attribute 'splitlines' (INFO) 2016-03-07 09:54:45,179 cmd_helper._ValidateAndLogCommand:153 [host]> /b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s AG8604420GI4IGC shell '( /system/bin/screencap -p /data/local/tmp/temp_file-f6e3c7272ff0.png );echo %$?' (INFO) 2016-03-07 09:54:45,666 cmd_helper._ValidateAndLogCommand:153 [host]> /b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s AG8604420GI4IGC shell '( dumpsys SurfaceFlinger --latency SurfaceView );echo %$?' (INFO) 2016-03-07 09:54:46,556 cmd_helper._ValidateAndLogCommand:153 [host]> /b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s AG8604420GI4IGC pull /data/local/tmp/temp_file-f6e3c7272ff0.png /tmp/tmp_xGR5S.png (INFO) 2016-03-07 09:54:46,768 cmd_helper._ValidateAndLogCommand:153 [host]> /b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s AG8604420GI4IGC shell '( dumpsys SurfaceFlinger --latency SurfaceView );echo %$?' (INFO) 2016-03-07 09:54:46,857 cmd_helper._ValidateAndLogCommand:153 [host]> /b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s AG8604420GI4IGC shell 'rm -f /data/local/tmp/temp_file-f6e3c7272ff0.png' Traceback (most recent call last): File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 84, in _RunStoryAndProcessErrorIfNeeded state.RunStory(results) File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 323, in RunStory self._current_page.Run(self) File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/page/__init__.py", line 88, in Run self.RunPageInteractions(action_runner) File "/b/build/slave/Android_One_Perf__1_/build/src/tools/perf/page_sets/tough_filters_cases.py", line 21, in RunPageInteractions action_runner.Wait(10) File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/page/action_runner.py", line 706, in __exit__ self.End() File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/page/action_runner.py", line 726, in End self._label, self._flags)) File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/browser/web_contents.py", line 161, in ExecuteJavaScript statement, context_id=None, timeout=timeout) File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/browser/web_contents.py", line 194, in ExecuteJavaScriptInContext expr, context_id=context_id, timeout=timeout) File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py", line 35, in inner inspector_backend._ConvertExceptionFromInspectorWebsocket(e) File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py", line 32, in inner return func(inspector_backend, *args, **kwargs) File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py", line 185, in ExecuteJavaScript self._runtime.Execute(expr, context_id, timeout) File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_runtime.py", line 21, in Execute self.Evaluate(expr + '; 0;', context_id, timeout) File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_runtime.py", line 45, in Evaluate res = self._inspector_websocket.SyncRequest(request, timeout) File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_websocket.py", line 110, in SyncRequest res = self._Receive(timeout) File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_websocket.py", line 149, in _Receive data = self._socket.recv() File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/third_party/websocket-client/websocket.py", line 596, in recv opcode, data = self.recv_data() File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/third_party/websocket-client/websocket.py", line 606, in recv_data frame = self.recv_frame() File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/third_party/websocket-client/websocket.py", line 637, in recv_frame self._frame_header = self._recv_strict(2) File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/third_party/websocket-client/websocket.py", line 746, in _recv_strict bytes = self._recv(shortage) File "/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/third_party/websocket-client/websocket.py", line 732, in _recv raise WebSocketTimeoutException(e.message) TimeoutException: ******************************************************************************** (/b/build/slave/Android_One_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py:309 _ConvertExceptionFromInspectorWebsocket) The app is probably crashed: