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

Issue 809594 link

Starred by 1 user
Status: Duplicate
Merged: issue 809233
Owner:
geoffl...@chromium.org
Closed: Aug 8
Cc:
danakj@chromium.org
█ kbr@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

Blocked on:
issue 810411


Sign in to add a comment

WebglConformance_conformance2_textures_misc_copy_texture_image_same_texture failing on Win10 NVIDIA release ANGLE GL

Project Member Reported by cwallez@chromium.org, Feb 6 2018 
The first failing build is https://ci.chromium.org/buildbot/chromium.gpu.fyi/Win10%20Release%20%28NVIDIA%29/4908

that has a WebGL roll in the blamelist https://chromium.googlesource.com/external/khronosgroup/webgl.git/+log/d458ada..98a3d3b

This roll adds this test so this is a pre-existing bug. Geoff, since it is on the ANGLE GL backend on Windows, can you TAL?

Comment 1 by kbr@chromium.org, Feb 6 2018 

Corentin, as ANGLE wrangler could you please add a failure suppression to get the bot green again?

Comment 2 by cwallez@chromium.org, Feb 6 2018 

Yes, it failed presubmit, will upload it again.
Project Member

Comment 3 by bugdroid1@chromium.org, Feb 6 2018 

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

commit 7818127b40c931505e500b8203206ae3285406ec
Author: Corentin Wallez <cwallez@chromium.org>
Date: Tue Feb 06 19:55:37 2018

Suppress failing WebGL CTS tests after roll

BUG= chromium:809594 
BUG=chromium:809595
TBR=kbr@chromium.org
NOTRY=true

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;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
Change-Id: Ieaab1775fafa95765f21c9d736539df3e85dff4b
Reviewed-on: https://chromium-review.googlesource.com/905098
Commit-Queue: Corentin Wallez <cwallez@chromium.org>
Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534761}
[modify] https://crrev.com/7818127b40c931505e500b8203206ae3285406ec/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py

Comment 4 by danakj@chromium.org, Feb 8 2018

Components: Internals>GPU>ANGLE
Labels: -Pri-3 Pri-2
There's a few other tests failing on this bot. Would it be related?

- WebglConformance_conformance_glsl_misc_non_ascii_comments_vert

https://ci.chromium.org/buildbot/chromium.gpu.fyi/Win10%20Release%20%28NVIDIA%29/4944

[71/136] gpu_tests.webgl_conformance_integration_test.WebGLConformanceIntegrationTest.WebglConformance_conformance_glsl_misc_non_ascii_comments_vert failed unexpectedly 1.9240s:
  
  Traceback (most recent call last):
    _RunGpuTest at content\test\gpu\gpu_tests\gpu_integration_test.py:132
      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:213
      self.fail(self._WebGLTestMessages(self.tab))
    fail at c:\infra-system\bin\lib\unittest\case.py:410
      raise self.failureException(msg)
  AssertionError: Unable to fetch WebGL rendering context for Canvas
  FAIL Unable to fetch WebGL rendering context for Canvas
  context does not exist
  FAIL context does not exist
  
- WebGLConformanceIntegrationTest.WebglConformance_conformance2_textures_video_tex_3d_rg16f_rg_float

https://ci.chromium.org/buildbot/chromium.gpu.fyi/Win10%20Debug%20%28NVIDIA%29/2790

[51/136] gpu_tests.webgl_conformance_integration_test.WebGLConformanceIntegrationTest.WebglConformance_conformance2_textures_video_tex_3d_rg16f_rg_float failed unexpectedly 4.6570s:
  
  Traceback (most recent call last):
    _RunGpuTest at content\test\gpu\gpu_tests\gpu_integration_test.py:132
      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:213
      self.fail(self._WebGLTestMessages(self.tab))
    fail at c:\infra-system\bin\lib\unittest\case.py:410
      raise self.failureException(msg)
  AssertionError: shouldBe 255,0,0
  at (4, 4) expected: 255,0,0 was 0,0,0

- WebglConformance_conformance2_textures_svg_image_tex_3d_rg32f_rg_float
- WebglConformance_deqp_functional_gles3_shaderpackingfunction

https://ci.chromium.org/buildbot/chromium.gpu.fyi/Win10%20Release%20%28NVIDIA%29/4943

[54/135] gpu_tests.webgl_conformance_integration_test.WebGLConformanceIntegrationTest.WebglConformance_conformance2_textures_svg_image_tex_3d_rg32f_rg_float failed unexpectedly 1.9870s:
  
  Traceback (most recent call last):
    _RunGpuTest at content\test\gpu\gpu_tests\gpu_integration_test.py:132
      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:213
      self.fail(self._WebGLTestMessages(self.tab))
    fail at c:\infra-system\bin\lib\unittest\case.py:410
      raise self.failureException(msg)
  AssertionError: Unable to fetch WebGL rendering context for Canvas
  FAIL Unable to fetch WebGL rendering context for Canvas
  Uncaught TypeError: Cannot read property 'RG' of null

  AssertionError: pack_unpack.packsnorm2x16_lowp_vertex: Result comparison failed
  Init testcase: pack_unpack
  Init testcase: pack_unpack.packsnorm2x16_lowp_vertex
  Executing shader for 100 input values
  ERROR: Mismatch in value 1, expected packSnorm2x16(-1,1) = 2147450881, got 0
    diffs = (32769, 32767), max diff = 129
  ERROR: Mismatch in value 2, expected packSnorm2x16(0.5,-0.5) = -1073725441, got 0
    diffs = (16383, 49152), max diff = 129
  ERROR: Mismatch in value 3, expected packSnorm2x16(-1.5,1.5) = 2147450881, got 0
    diffs = (32769, 32767), max diff = 129
  ERROR: Mismatch in value 4, expected packSnorm2x16(0.25,-0.75) = -1610604545, got 0
    diffs = (8191, 40960), max diff = 129
  ERROR: Mismatch in value 5, expected packSnorm2x16(0.29560347087681293,1.0828318819403648) = 2147427798, got 0
    diffs = (9686, 32767), max diff = 129
  ERROR: Mismatch in value 6, expected packSnorm2x16(1.0519909020513296,-0.4195935931056738) = -901021697, got 0
    diffs = (32767, 51787), max diff = 129
  ERROR: Mismatch in value 7, expected packSnorm2x16(0.9711288567632437,-1.237842282280326) = -2147386292, got 0
    diffs = (31820, 32769), max diff = 129
  ERROR: Mismatch in value 8, expected packSnorm2x16(0.8873642235994339,-0.7703863363713026) = -1654361708, got 0
    diffs = (29076, 40292), max diff = 129
  ERROR: Mismatch in value 9, expected packSnorm2x16(0.38550548255443573,0.41121426969766617) = 883044695, got 0
    diffs = (12631, 13474), max diff = 129
  ERROR: Mismatch in value 10, expected packSnorm2x16(0.294991759583354,0.485550370067358) = 1042687425, got 0
    diffs = (9665, 15910), max diff = 129


It's like a different test every bot run so it's hard to say exactly what, but it seems like contexts are not valid flakily?

Comment 5 by kbr@chromium.org, Feb 10 2018

Blockedon: 810411
Is this a duplicate of  Issue 810411 ?
Project Member

Comment 6 by bugdroid1@chromium.org, Feb 12 2018 

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

commit 67ba0521d38d3a172f6f8719484d79dddfe74b6a
Author: Jamie Madill <jmadill@chromium.org>
Date: Mon Feb 12 16:43:29 2018

WebGL: Upgrade shaderpackingfunction expectation to fail.

This flaky expectation was not sufficient to prevent the test from
flaking multiple times in a run, to the point where it would cause
the test step to flake. Change this to a failure suppression so
that the tests can pass.

Bug:  809594 
Tbr: brianderson@chromium.org
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;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
Change-Id: I0d2ef736a0d7b5c6c3af1e761d6bca463408de78
Reviewed-on: https://chromium-review.googlesource.com/913810
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536101}
[modify] https://crrev.com/67ba0521d38d3a172f6f8719484d79dddfe74b6a/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py
Project Member

Comment 7 by bugdroid1@chromium.org, Feb 14 2018 

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

commit 0021eb9caf5efe5a9bec783122c4a6dfe85eba4b
Author: Jamie Madill <jmadill@chromium.org>
Date: Wed Feb 14 20:39:27 2018

WebGL: Upgrade shadercommonfunction expectation to fail.

This flaky expectation was not sufficient to prevent the test from
flaking multiple times in a run, to the point where it would cause
the test step to flake. Change this to a failure suppression so
that the tests can pass.

Bug:  809594 , 795030
Tbr: kbr@chromium.org
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;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
Change-Id: I649b038bea22e3e31c107f9791df648152556aba
Reviewed-on: https://chromium-review.googlesource.com/919522
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536805}
[modify] https://crrev.com/0021eb9caf5efe5a9bec783122c4a6dfe85eba4b/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py

Comment 8 by kbr@chromium.org, Aug 8

Mergedinto: 809233
Status: Duplicate (was: Assigned)
Duplicating this into  Issue 809233 .
Project Member

Comment 9 by bugdroid1@chromium.org, Aug 23 

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

commit 548ac6ffdaac420fbc90a96f09104ef401bc2c38
Author: Corentin Wallez <cwallez@chromium.org>
Date: Thu Aug 23 13:42:45 2018

Suppress Win/Intel/Passthrough/OpenGL WebGL CTS failures

These are the initial suppressions because the
webgl[2]_gl_passthrough_conformance_tests just got added on Win/Intel.

TBR=kbr@chromium.org

BUG=angleproject:2760
BUG=chromium:602688
BUG= chromium:809594 
BUG= chromium:864524 
BUG= chromium:876777 

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I88cc85a313ab09fafca5f44129a7f85cc99ddcb2
Reviewed-on: https://chromium-review.googlesource.com/1186462
Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Commit-Queue: Corentin Wallez <cwallez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#585470}
[modify] https://crrev.com/548ac6ffdaac420fbc90a96f09104ef401bc2c38/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py
►

Sign in to add a comment