New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 755657 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: ----
Type: ----



Sign in to add a comment

smoothness.tough_canvas_cases failing on chromium.perf/Android One Perf

Project Member Reported by simonhatch@chromium.org, Aug 15 2017

Issue description

smoothness.tough_canvas_cases failing on chromium.perf/Android One Perf

Builders failed on: 
- Android One Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf



 
Failing page:
 - tough_canvas_cases/canvas_toBlob.html


Snippet from log:

Exception raised when cleaning story run: 

Traceback (most recent call last):
  _RunStoryAndProcessErrorIfNeeded at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/story_runner.py:132
    test.DidRunPage(state.platform)
  traced_function at /b/swarming/w/ir/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:75
    return func(*args, **kwargs)
  DidRunPage at /b/swarming/w/ir/tools/perf/measurements/smoothness.py:67
    self._tbm.DidRunStory(platform, self._results)
  DidRunStory at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/web_perf/timeline_based_measurement.py:310
    trace_result = platform.tracing_controller.StopTracing()
  StopTracing at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/core/tracing_controller.py:47
    return self._tracing_controller_backend.StopTracing()
  StopTracing at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:109
    self._IssueClockSyncMarker()
  _IssueClockSyncMarker at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:213
    self._RecordIssuerClockSyncMarker)
  RecordClockSyncMarker at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py:178
    raise ChromeClockSyncError('Cannot issue clock sync. No devtools clients')
ChromeClockSyncError: Cannot issue clock sync. No devtools clients

Locals:
  devtools_clients                             : []
  record_controller_clock_sync_marker_callback : <bound method TracingControllerBackend._RecordIssuerClockSyncMarker of <telemetry.internal.platform.tracing_controller_backend.TracingControllerBackend object at 0x7fddcdbd2cd0>>
  sync_id                                      : '04600dcb-8b5d-409e-ad09-043ea349bee4'
Project Member

Comment 3 by bugdroid1@chromium.org, Aug 15 2017

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

commit bd1762eccd6b04bbbf3b33463fb76380aec3d1c9
Author: Simon <simonhatch@chromium.org>
Date: Tue Aug 15 20:58:23 2017

Disable smoothness.tough_canvas_cases canvas_toBlob.html on Android One.

TBR=rnephew@chromium.org

Bug:  755657 
Change-Id: If83874757390c4b43d411439635ff8ee6aa81b14
Reviewed-on: https://chromium-review.googlesource.com/615783
Reviewed-by: Simon Hatch <simonhatch@chromium.org>
Commit-Queue: Simon Hatch <simonhatch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#494537}
[modify] https://crrev.com/bd1762eccd6b04bbbf3b33463fb76380aec3d1c9/tools/perf/benchmarks/smoothness.py

Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Aug 16 2017


=== BISECT JOB RESULTS ===
NO Test failure found

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : smoothness.tough_canvas_cases
  Metric       : benchmark_duration/benchmark_duration

Revision             Exit Code      N
chromium@492603      1 +- N/A       10      good
chromium@492888      1 +- N/A       10      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 smoothness.tough_canvas_cases

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8971166829750586192


For feedback, file a bug with component Speed>Bisection
Status: WontFix (was: Available)
This is no longer failing, marking as WontFix

Sign in to add a comment