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

Issue 747540 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 742315
Owner:
OOO until 2019-01-24
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug

Blocking:
issue 730036



Sign in to add a comment

gpu_tests.maps_integration_test.MapsIntegrationTest.Maps_maps_004 is flaky on Mac Release

Project Member Reported by flackr@chromium.org, Jul 21 2017

Issue description

This seems to fail about 2% of runs.

Traceback (most recent call last):
  _RunGpuTest at content/test/gpu/gpu_tests/gpu_integration_test.py:125
    self.RunActualGpuTest(url, *args)
  RunActualGpuTest at content/test/gpu/gpu_tests/maps_integration_test.py:126
    screenshot = tab.Screenshot(5)
  traced_function at third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:52
    return func(*args, **kwargs)
  Screenshot at third_party/catapult/telemetry/telemetry/internal/browser/tab.py:117
    return self._inspector_backend.Screenshot(timeout)
  traced_function at third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:52
    return func(*args, **kwargs)
  inner at third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py:39
    inspector_backend._ConvertExceptionFromInspectorWebsocket(e)
  traced_function at third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:52
    return func(*args, **kwargs)
  inner at third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py:36
    return func(inspector_backend, *args, **kwargs)
  Screenshot at third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py:142
    return self._page.CaptureScreenshot(timeout)
  CaptureScreenshot at third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_page.py:153
    res = self._inspector_websocket.SyncRequest(request, timeout)
  SyncRequest at third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_websocket.py:110
    res = self._Receive(timeout)
  _Receive at third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_websocket.py:149
    data = self._socket.recv()
  recv at third_party/catapult/telemetry/third_party/websocket-client/websocket/_core.py:293
    opcode, data = self.recv_data()
  recv_data at third_party/catapult/telemetry/third_party/websocket-client/websocket/_core.py:310
    opcode, frame = self.recv_data_frame(control_frame)
  recv_data_frame at third_party/catapult/telemetry/third_party/websocket-client/websocket/_core.py:323
    frame = self.recv_frame()
  recv_frame at third_party/catapult/telemetry/third_party/websocket-client/websocket/_core.py:357
    return self.frame_buffer.recv_frame()
  recv_frame at third_party/catapult/telemetry/third_party/websocket-client/websocket/_abnf.py:336
    self.recv_header()
  recv_header at third_party/catapult/telemetry/third_party/websocket-client/websocket/_abnf.py:286
    header = self.recv_strict(2)
  recv_strict at third_party/catapult/telemetry/third_party/websocket-client/websocket/_abnf.py:371
    bytes_ = self.recv(min(16384, shortage))
  _recv at third_party/catapult/telemetry/third_party/websocket-client/websocket/_core.py:427
    return recv(self.sock, bufsize)
  recv at third_party/catapult/telemetry/third_party/websocket-client/websocket/_socket.py:83
    raise WebSocketTimeoutException(message)
TimeoutException: 

It looks like it's timing out trying to take a screenshot.

For example, the 10 most recent failures:
https://build.chromium.org/p/chromium.gpu/builders/Mac%20Release%20%28Intel%29/builds/68776
https://build.chromium.org/p/chromium.gpu/builders/Mac%20Release%20%28Intel%29/builds/68765
https://build.chromium.org/p/chromium.gpu/builders/Mac%20Release%20%28Intel%29/builds/68749
https://build.chromium.org/p/chromium.gpu/builders/Mac%20Release%20%28Intel%29/builds/68705
https://build.chromium.org/p/chromium.gpu/builders/Mac%20Release%20%28Intel%29/builds/68611
https://build.chromium.org/p/chromium.gpu/builders/Mac%20Release%20%28Intel%29/builds/68580
https://build.chromium.org/p/chromium.gpu/builders/Mac%20Release%20%28Intel%29/builds/68532
https://build.chromium.org/p/chromium.gpu/builders/Mac%20Release%20%28Intel%29/builds/68510
https://build.chromium.org/p/chromium.gpu/builders/Mac%20Release%20%28Intel%29/builds/68443
https://build.chromium.org/p/chromium.gpu/builders/Mac%20Release%20%28Intel%29/builds/68322








 

Comment 1 by kbr@chromium.org, Jul 24 2017

Blocking: 730036
Cc: nedngu...@google.com xunji...@chromium.org
Components: Internals>GPU>Testing
Mergedinto: 742315
Status: Duplicate (was: Untriaged)
Thanks for reporting this. As far as I can tell this is the same problem as  Issue 742315 , where Telemetry's WPR server doesn't start up quickly enough and the browser fails to navigate to the test's page. Please reopen this bug or file a new one if the flakiness rate increases significantly (and, in particular, if it starts affecting the commit queue), but otherwise we'll wait for the rewrite of the WPR server.

Sign in to add a comment