New issue
Advanced search Search tips

Issue 592651 link

Starred by 1 user
Status: WontFix
Owner:
simonhatch@chromium.org
Closed: Mar 2016
Cc:
skyos...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug-Regression



Sign in to add a comment

smoothness.scrolling_tough_ad_cases failure on chromium.perf on Android Galaxy S5 Perf (1)

Project Member Reported by simonhatch@chromium.org, Mar 7 2016 
Revision range first seen:
Looks like it roughly started around Feb 22


Link to failing step log:
https://build.chromium.org/p/chromium.perf/builders/Android%20Galaxy%20S5%20Perf%20%281%29/builds/1813




Not super clear from log output what's going wrong, there's an error:


(INFO) 2016-03-07 07:39:00,954 cmd_helper._ValidateAndLogCommand:153  [host]> /b/build/slave/Android_Galaxy_S5_Perf__1_/build/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s 3208851faca351f3 shell '( logcat -d -t 500 );echo %$?'
Traceback (most recent call last):
  File "/b/build/slave/Android_Galaxy_S5_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_Galaxy_S5_Perf__1_/build/src/third_party/android_platform/development/scripts/stack", line 194, in main
    constants.CheckOutputDirectory()
  File "/b/build/slave/Android_Galaxy_S5_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_Galaxy_S5_Perf__1_/build/src/build/android/tombstones.py", line 273, in <module>
    sys.exit(main())
  File "/b/build/slave/Android_Galaxy_S5_Perf__1_/build/src/build/android/tombstones.py", line 255, in main
    constants.CheckOutputDirectory()
  File "/b/build/slave/Android_Galaxy_S5_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




And a few lines after that:

(INFO) 2016-03-07 07:39:02,870 cmd_helper._ValidateAndLogCommand:153  [host]> /b/build/slave/Android_Galaxy_S5_Perf__1_/build/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s 3208851faca351f3 shell 'rm -f /data/local/tmp/temp_file-e351328790999.png'
Traceback (most recent call last):
  File "/b/build/slave/Android_Galaxy_S5_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_Galaxy_S5_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 325, in RunStory
    self._current_page, self._current_tab, results)
  File "/b/build/slave/Android_Galaxy_S5_Perf__1_/build/src/tools/perf/measurements/smoothness.py", line 61, in ValidateAndMeasurePage
    self._tbm.Measure(tab.browser.platform, results)
  File "/b/build/slave/Android_Galaxy_S5_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/web_perf/timeline_based_measurement.py", line 281, in Measure
    trace_result = platform.tracing_controller.StopTracing()
  File "/b/build/slave/Android_Galaxy_S5_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/core/tracing_controller.py", line 39, in StopTracing
    return self._tracing_controller_backend.StopTracing()
  File "/b/build/slave/Android_Galaxy_S5_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py", line 124, in StopTracing
    '\n'.join(raised_exception_messages))
TracingControllerStoppedError: Exceptions raised when trying to stop tracing:
Traceback (most recent call last):
  File "/b/build/slave/Android_Galaxy_S5_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py", line 113, in StopTracing
    agent.StopAgentTracing(builder)
  File "/b/build/slave/Android_Galaxy_S5_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py", line 143, in StopAgentTracing
    '\n'.join(raised_execption_messages))
ChromeTracingStoppedError: Exceptions raised when trying to stop Chrome devtool tracing:
Error when trying to stop Chrome tracing on devtools at port localabstract:chrome_devtools_remote:
Traceback (most recent call last):
  File "/b/build/slave/Android_Galaxy_S5_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py", line 128, in StopAgentTracing
    client.StopChromeTracing(trace_data_builder)
  File "/b/build/slave/Android_Galaxy_S5_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/devtools_client_backend.py", line 348, in StopChromeTracing
    "console.time.toString().indexOf('[native code]') != -1;")
  File "/b/build/slave/Android_Galaxy_S5_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_Galaxy_S5_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py", line 197, in EvaluateJavaScript
    return self._runtime.Evaluate(expr, context_id, timeout)
  File "/b/build/slave/Android_Galaxy_S5_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_Galaxy_S5_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_Galaxy_S5_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_websocket.py", line 166, in _Receive
    self._HandleNotification(result)
  File "/b/build/slave/Android_Galaxy_S5_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_websocket.py", line 179, in _HandleNotification
    self._domain_handlers[domain_name](result)
  File "/b/build/slave/Android_Galaxy_S5_Perf__1_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py", line 282, in _HandleInspectorDomainNotification
    raise exception
DevtoolsTargetCrashException: Devtools target crashed
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, 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@376659         1           N/A         5           good
chromium@376815         1           N/A         5           bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 592651

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests smoothness.scrolling_tough_ad_cases
Test Metric: frame_times/swiffy_collection.html
Relative Change: 0.00%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/508
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9018812572069342784


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

Comment 4 by simonhatch@chromium.org, Mar 10 2016

Owner: simonhatch@chromium.org
Status: WontFix (was: Untriaged)
Not sure what fixed this, but it's been green for several days now, so closing this.
►

Sign in to add a comment