New issue
Advanced search Search tips

Issue 748110 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

pixel_test and screenshot_sync_tests flaky on Mac bots

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

Issue description

The Mac Release (Intel) and Mac Retina Debug (AMD) bots have both had fairly flaky results for the pixel_test and screenshot_sync_tests.

Recent runs suggest roughly a 10% failure rate:
https://build.chromium.org/p/chromium.gpu/builders/Mac%20Release%20%28Intel%29?numbuilds=200
https://build.chromium.org/p/chromium.gpu/builders/Mac%20Retina%20Debug%20%28AMD%29?numbuilds=200

I'm not sure if the failure cause is the same. The Mac Retina Debug flakiness looks like it might have started sometime around Jul 20th / 21st and the other one may start around the same date (need to scrape some older build results since it's before the last 200)
 

Comment 1 by junov@chromium.org, Aug 7 2017

Status: Available (was: Untriaged)

Comment 2 by gab@chromium.org, Aug 8 2017

Not sure what sheriffs can do with this.. it's too old to determine regression range now...
Cc: bajones@chromium.org
Adding bajones@chromium.org from src/content/test/gpu/OWNERS as triage for this component doesn't seem to work.

As of Aug 18 the error still seems to be around, but at lower than 10%, rather close to 5% of the builds. Not a big deal, but should at least be looked at by someone.

Example error (pixel_test):

[1/42] gpu_tests.pixel_integration_test.PixelIntegrationTest.Pixel_2DCanvasWebGL failed unexpectedly 42.5443s:
  Found crashpad_database_util
  No minidump found via crashpad_database_util
  Found crashpad_database_util
  No minidump found via crashpad_database_util
  Can't get standard output with --show-stdout
  
  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/pixel_integration_test.py:125
      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: 


Labels: -Sheriff-Chromium
assigning to bajones@ to route further or investigate.
Cc: -bajones@chromium.org
Owner: bajones@chromium.org
Status: Assigned (was: Untriaged)
Labels: -Pri-2 Pri-1
I don't know if this cause is the same, but:

https://uberchromegw.corp.google.com/i/chromium.gpu/builders/Mac%20Release%20%28Intel%29/builds/72980

These tests are still failing on mac intel.

bajones@, can you take a peek at this?

Sign in to add a comment