Revision range first seen: ?????? (before 10/25)
Link to failing step log: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus7v2%20Perf%20%282%29/builds/3319/steps/start_with_url.cold.startup_pages.reference/logs/stdio
This seems to be happening across all Chrome devices.
Excerpt from log:
Traceback (most recent call last):
File "/b/rr/tmpkpY_Zi/w/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 89, in _RunStoryAndProcessErrorIfNeeded
test.Measure(state.platform, results)
File "/b/rr/tmpkpY_Zi/w/src/third_party/catapult/telemetry/telemetry/web_perf/timeline_based_measurement.py", line 284, in Measure
trace_result = platform.tracing_controller.StopTracing()
File "/b/rr/tmpkpY_Zi/w/src/third_party/catapult/telemetry/telemetry/core/tracing_controller.py", line 47, in StopTracing
return self._tracing_controller_backend.StopTracing()
File "/b/rr/tmpkpY_Zi/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py", line 108, in StopTracing
self._IssueClockSyncMarker()
File "/b/rr/tmpkpY_Zi/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py", line 203, in _IssueClockSyncMarker
self._RecordIssuerClockSyncMarker)
File "/b/rr/tmpkpY_Zi/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py", line 175, in RecordClockSyncMarker
raise ChromeClockSyncError('Cannot issue clock sync. No devtools clients')
ChromeClockSyncError: Cannot issue clock sync. No devtools clients
This indicates that Chrome is crashing.
The error always seems to be happening on the kapook.com story, so I'm going to go ahead and disable story that for now.
gabadie@, could you please fix this or remove kabook.com if you're no longer interested in this story?
If the test is disabled, please downgrade to Pri-2.
Comment 1 by bugdroid1@chromium.org
, Nov 21 2016