New issue
Advanced search Search tips

Issue 795950 link

Starred by 1 user

Issue metadata

Status: WontFix
Merged: issue 797368
Owner: ----
Closed: Jan 10
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

WebglConformance_conformance2_textures_canvas_sub_rectangle_tex_2d_rgb9_e5_rgb_half_float flaky on mac_optional_gpu_tests_rel

Project Member Reported by kbr@chromium.org, Dec 18 2017

Issue description

Flakes seen here:

https://ci.chromium.org/buildbot/tryserver.chromium.mac/mac_optional_gpu_tests_rel/19110
https://ci.chromium.org/buildbot/tryserver.chromium.mac/mac_optional_gpu_tests_rel/19084

In https://ci.chromium.org/buildbot/tryserver.chromium.mac/mac_optional_gpu_tests_rel/19084 the test failed:

  AssertionError: should be 0,0,255
  at (15, 1) expected: 0,0,255 was 0,255,255
  FAIL should be 0,0,255
  at (15, 1) expected: 0,0,255 was 0,255,255
  should be 0,0,255
  at (31, 1) expected: 0,0,255 was 0,255,255
  FAIL should be 0,0,255
  at (31, 1) expected: 0,0,255 was 0,255,255
  should be 0,0,255
  at (4, 16) expected: 0,0,255 was 0,255,255
  FAIL should be 0,0,255
  at (4, 16) expected: 0,0,255 was 0,255,255
  should be 0,0,255
  at (20, 16) expected: 0,0,255 was 0,255,255
  FAIL should be 0,0,255
  at (20, 16) expected: 0,0,255 was 0,255,255
  should be 0,0,255
  at (15, 1) expected: 0,0,255 was 0,255,255
  FAIL should be 0,0,255
  at (15, 1) expected: 0,0,255 was 0,255,255
  should be 0,0,255
  at (31, 1) expected: 0,0,255 was 0,255,255
  FAIL should be 0,0,255
  at (31, 1) expected: 0,0,255 was 0,255,255


In WebglConformance_conformance2_textures_canvas_sub_rectangle_tex_2d_rgb9_e5_rgb_float the test timed out:

https://chromium-swarm.appspot.com/task?id=3a833b2f39e3a510&refresh=10&show_raw=1

[9/137] gpu_tests.webgl_conformance_integration_test.WebGLConformanceIntegrationTest.WebglConformance_conformance2_textures_canvas_sub_rectangle_tex_2d_rgb9_e5_rgb_float failed unexpectedly 302.2095s:

...

    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: 


This test doesn't seem to use any asynchrony so it's unclear how it could intermittently time out.

 

Comment 1 by piman@chromium.org, Jan 9 2018

Mergedinto: 797368
Status: Duplicate (was: Untriaged)
Status: Available (was: Duplicate)
Note that the failing test is rgb_half_float on ATI GPU.
The timing out test is rgb_float on Intel GPU.
The second one probably is a duplicate of  issue 797368 , but not the first one.
Project Member

Comment 3 by sheriffbot@chromium.org, Jan 10

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)
I can't find any suppressions for this, and I'm not finding evidence it's been seen more recently. Closing.

Sign in to add a comment