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

Issue 658842 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

WebglConformance_conformance2_buffers_uniform_buffers is flaky on Linux Release (ATI)

Project Member Reported by ynovikov@chromium.org, Oct 24 2016

Issue description

Started in https://build.chromium.org/p/chromium.gpu.fyi/builders/Linux%20Release%20%28ATI%29/builds/49431

Also failed in
https://build.chromium.org/p/chromium.gpu.fyi/builders/Linux%20Release%20%28ATI%29/builds/49434
https://build.chromium.org/p/chromium.gpu.fyi/builders/Linux%20Release%20%28ATI%29/builds/49439
https://build.chromium.org/p/chromium.gpu.fyi/builders/Linux%20Release%20%28ATI%29/builds/49441

The only CL in WebGL / ANGLE area I see is https://chromium-review.googlesource.com/#/c/399682/, though I have no idea if it's related.
Since it's flaky it might have been caused by something before that.

Log says:

WebglConformance_conformance2_buffers_uniform_buffers (gpu_tests.webgl_conformance_integration_test.WebGLConformanceIntegrationTest) ... [21132:21132:1021/205203:INFO:CONSOLE(172)] "WebGL: INVALID_OPERATION: bindBuffer: attempt to bind a deleted buffer", source: http://127.0.0.1:49067/third_party/webgl/src/sdk/tests/conformance2/buffers/uniform-buffers.html?webglVersion=2 (172)
[21132:21132:1021/205203:INFO:CONSOLE(11)] "Uniform offsets are not well aligned", source:  (11)
[21132:21132:1021/205203:INFO:CONSOLE(11)] "*** Error compiling FRAGMENT_SHADER '[object WebGLShader]':ERROR: 0:13: 'UBOGreen' : redefinition interface block member name
", source:  (11)
[21132:21132:1021/205203:INFO:CONSOLE(11)] "Error in compiling shader", source:  (11)
[21132:21132:1021/205203:INFO:CONSOLE(11)] "FAIL Uniform offsets are not well aligned", source:  (11)
[21132:21132:1021/205203:INFO:CONSOLE(11)] "Uniform offsets are not well aligned", source:  (11)
[21132:21132:1021/205203:INFO:CONSOLE(11)] "FAIL Uniform offsets are not well aligned", source:  (11)
[21132:21132:1021/205203:INFO:CONSOLE(11)] "Uniform offsets are not well aligned", source:  (11)
[21132:21132:1021/205203:INFO:CONSOLE(11)] "FAIL Uniform offsets are not well aligned", source:  (11)

Traceback (most recent call last):
  _RunGpuTest at content/test/gpu/gpu_tests/gpu_integration_test.py:78
    self.RunActualGpuTest(url, *args)
  RunActualGpuTest at content/test/gpu/gpu_tests/webgl_conformance_integration_test.py:196
    getattr(self, test_name)(test_path, *args[1:])
  _RunConformanceTest at content/test/gpu/gpu_tests/webgl_conformance_integration_test.py:210
    self._CheckTestCompletion()
  _CheckTestCompletion at content/test/gpu/gpu_tests/webgl_conformance_integration_test.py:206
    self.fail(self._WebGLTestMessages(self.tab))
  fail at /usr/lib/python2.7/unittest/case.py:412
    raise self.failureException(msg)
AssertionError: Uniform offsets are not well aligned
*** Error compiling FRAGMENT_SHADER '[object WebGLShader]':ERROR: 0:13: 'UBOGreen' : redefinition interface block member name

Error in compiling shader
FAIL Uniform offsets are not well aligned
Uniform offsets are not well aligned
FAIL Uniform offsets are not well aligned
Uniform offsets are not well aligned
FAIL Uniform offsets are not well aligned

Locals:
  msg : u"Uniform offsets are not well aligned\n*** Error compiling FRAGMENT_SHADER '[object WebGLShader]':ERROR: 0:13: 'UBOGreen' : redefinition interface block member name\n\x00\nError in compiling shader\nFAIL Uniform offsets are not well aligned\nUniform offsets are not well aligned\nFAIL Uniform offsets are not well aligned\nUniform offsets are not well aligned\nFAIL Uniform offsets are not well aligned\n"

 
Components: Blink>WebGL
Also fails on Linux Release (AMD R7 240)
Project Member

Comment 2 by bugdroid1@chromium.org, Oct 25 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b73b48dee7cd47c37f8ff58a3c4461b28554c54c

commit b73b48dee7cd47c37f8ff58a3c4461b28554c54c
Author: ynovikov <ynovikov@chromium.org>
Date: Tue Oct 25 01:35:32 2016

Suppress WebGL 2 conformance failures on Linux bots.

BUG= 655147 ,  658832 , 658842, 658844,  658898 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2445973002
Cr-Commit-Position: refs/heads/master@{#427220}

[modify] https://crrev.com/b73b48dee7cd47c37f8ff58a3c4461b28554c54c/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py

Marking it as Flaky is not good enough for Linux Release (AMD R7 240), it still manages to fail after 3 retries https://build.chromium.org/p/chromium.gpu.fyi/builders/Linux%20Release%20%28AMD%20R7%20240%29/builds/614
Though sometimes it passes
https://build.chromium.org/p/chromium.gpu.fyi/builders/Linux%20Release%20%28AMD%20R7%20240%29/builds/613

Will mark as Fail
Project Member

Comment 4 by bugdroid1@chromium.org, Oct 26 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ab7bd32ff39911350337f3b6cc9a5d5634733bfa

commit ab7bd32ff39911350337f3b6cc9a5d5634733bfa
Author: ynovikov <ynovikov@chromium.org>
Date: Wed Oct 26 01:56:58 2016

Harder suppress WebGL 2 conformance failures on Linux AMD bots.

BUG=658842, 658844
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2451003002
Cr-Commit-Position: refs/heads/master@{#427576}

[modify] https://crrev.com/ab7bd32ff39911350337f3b6cc9a5d5634733bfa/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py

Comment 5 by enne@chromium.org, Jan 30 2017

Cc: zmo@chromium.org
Status: Available (was: Untriaged)
Seems to still be marked as failing.  Marking this as available.
Project Member

Comment 6 by sheriffbot@chromium.org, Feb 21 2018

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. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by kbr@chromium.org, Feb 21 2018

Labels: -Hotlist-Recharge-Cold
Status: Available (was: Untriaged)
Cc: -oetu...@nvidia.com

Sign in to add a comment