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

Issue 695002 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
OOO until 2019-01-24
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 649485



Sign in to add a comment

"webgl_conformance_tests (with patch)" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Feb 22 2017

Issue description

"webgl_conformance_tests (with patch)" is flaky.

This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label.

We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLwsSBUZsYWtlIiR3ZWJnbF9jb25mb3JtYW5jZV90ZXN0cyAod2l0aCBwYXRjaCkM.



This flaky test/step was previously tracked in  issue 682844 .
 

Comment 1 by treib@chromium.org, Feb 23 2017

Owner: kbr@chromium.org
Status: Assigned (was: Untriaged)
The failures seem to be all in different tests. Not sure what can be done here from the sheriffs' side.

kbr, any ideas?

Comment 2 by kbr@chromium.org, Feb 24 2017

Blocking: 649485
Cc: kainino@chromium.org
Components: Tests>Telemetry Blink>WebGL
Labels: Hotlist-PixelWrangler
These two failures:

WebglConformance_conformance_misc_type_conversion_test
https://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_ng/builds/392534
https://chromium-swarm.appspot.com/task?id=347b1e2f1590d710&refresh=10&show_raw=1

and:

WebglConformance_conformance_extensions_angle_instanced_arrays_out_of_bounds
https://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_ng/builds/392366
https://chromium-swarm.appspot.com/task?id=347a8641a5e0c510&refresh=10&show_raw=1

were timeouts while Telemetry was talking to the browser via DevTools. There was no minidump. Maybe the renderer process hung? No evidence of what went wrong.

-----
Traceback (most recent call last):
  _RunGpuTest at content/test/gpu/gpu_tests/gpu_integration_test.py:73
    self.RunActualGpuTest(url, *args)
  RunActualGpuTest at content/test/gpu/gpu_tests/webgl_conformance_integration_test.py:203
    getattr(self, test_name)(test_path, *args[1:])
  _RunConformanceTest at content/test/gpu/gpu_tests/webgl_conformance_integration_test.py:217
    self._CheckTestCompletion()
  _CheckTestCompletion at content/test/gpu/gpu_tests/webgl_conformance_integration_test.py:212
    if not self._DidWebGLTestSucceed(self.tab):
  _DidWebGLTestSucceed at content/test/gpu/gpu_tests/webgl_conformance_integration_test.py:332
    return tab.EvaluateJavaScript2('webglTestHarness._allTestSucceeded')
  traced_function at third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:52
    return func(*args, **kwargs)
  EvaluateJavaScript2 at third_party/catapult/telemetry/telemetry/internal/browser/web_contents.py:199
    return self.EvaluateJavaScript(*args, **kwargs)
  traced_function at third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:52
    return func(*args, **kwargs)
  EvaluateJavaScript at third_party/catapult/telemetry/telemetry/internal/browser/web_contents.py:167
    return self._inspector_backend.EvaluateJavaScript(*args, **kwargs)
  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:40
    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:37
    return func(inspector_backend, *args, **kwargs)
  EvaluateJavaScript at third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py:244
    return self._runtime.Evaluate(expression, context_id, timeout)
  Evaluate at third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_runtime.py:45
    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: 
********************************************************************************
(/b/s/w/ir_HOk29/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py:489 _ConvertExceptionFromInspectorWebsocket) The app is probably crashed:

Found Minidump: False
Stack Trace:
********************************************************************************
	No crash dump found.
********************************************************************************
-----

WebglConformance_conformance_glsl_misc_shader_with_non_reserved_words
https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_ng/builds/387119

This was  Issue 649485 .

Comment 3 by kbr@chromium.org, Feb 24 2017

Labels: -Pri-1 Pri-2
Note: if a pattern emerges regarding hangs then we'll mark tests flaky. Until then we'll monitor chromium-try-flakes.

As per offline conversation with kbr@: I'll check in if there are more flakes by end of day, and I'll remove the Sheriff label if not.
Labels: -Sheriff-Chromium
It's approaching end of day for me and there are no new flake reports, so I'm removing the sheriff label.

Comment 7 by kbr@chromium.org, Feb 28 2017

Status: WontFix (was: Assigned)
Thanks Fady for checking. I think this round of flakes is understood, and there's no widespread issue ongoing. Let's close this as WontFix, expecting chromium-try-flakes to file a new bug if it reoccurs.

Sign in to add a comment