New issue
Advanced search Search tips

Issue 778365 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Oct 2017
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

WebglConformance_conformance_glsl_constructors_glsl_construct_mat2 failing on Win10 Release (Intel HD 630)

Project Member Reported by khushals...@chromium.org, Oct 25 2017

Issue description

It started failing with this build: https://build.chromium.org/p/chromium.gpu.fyi/builders/Win10%20Release%20%28Intel%20HD%20630%29/builds/881.

Here's the error log:
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\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:\b\depot_tools\win_tools-2_7_6_bin\python\bin\lib\unittest\case.py:412
      raise self.failureException(msg)
  AssertionError: should be green
  at (0, 0) expected: 0,255,0,255 was 255,0,0,255
  *** Error compiling VERTEX_SHADER '[object WebGLShader]':ERROR: 0:11: 'constructor' : constructor does not have any arguments
  
    *** Error compiling FRAGMENT_SHADER '[object WebGLShader]':ERROR: 0:11: 'constructor' : constructing matrix from matrix can only take one argument
  
    Locals:
    msg : u"should be green\nat (0, 0) expected: 0,255,0,255 was 255,0,0,255\n*** Error compiling VERTEX_SHADER '[object WebGLShader]':ERROR: 0:11: 'constructor' : constructor does not have any arguments\n\x00\n*** Error compiling FRAGMENT_SHADER '[object WebGLShader]':ERROR: 0:9: 'constructor' : constructor does not have any arguments\n\x00\n*** Error compiling VERTEX_SHADER '[object WebGLShader]':ERROR: 0:11: 'constructor' : not enough data provided for construction\n\x00\n*** Error compiling FRAGMENT_SHADER '[o ... TEX_SHADER '[object WebGLShader]':ERROR: 0:14: 'constructor' : constructing matrix from matrix can only take one argument\n\x00\n*** Error compiling FRAGMENT_SHADER '[object WebGLShader]':ERROR: 0:12: 'constructor' : constructing matrix from matrix can only take one argument\n\x00\n*** Error compiling VERTEX_SHADER '[object WebGLShader]':ERROR: 0:15: 'constructor' : too many arguments\n\x00\n*** Error compiling FRAGMENT_SHADER '[object WebGLShader]':ERROR: 0:13: 'constructor' : too many arguments\n\x00\n" (truncated)

Most likely its this change: https://chromium.googlesource.com/chromium/src/+/6cb6e5c0e17babc4b68a2e4a2a628beff31b64d5
 
Project Member

Comment 1 by bugdroid1@chromium.org, Oct 25 2017

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

commit 6cb050470520e652eeb894fd01f87ca6a2d6034a
Author: Geoff Lang <geofflang@chromium.org>
Date: Wed Oct 25 20:39:39 2017

Supress WebGL1 failure with Win/OpenGL/passthrough decoder.

WebglConformance_conformance_glsl_constructors_glsl_construct_mat2
started failing when enabling it on Windows/Intel/OpenGL.

TBR=zmo@chromium.org
NOTRY=true

BUG= 778365 

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: Ia224b0ec1ec1efffb1038b13ff2333d701bd61da
Reviewed-on: https://chromium-review.googlesource.com/738332
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Reviewed-by: Geoff Lang <geofflang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#511575}
[modify] https://crrev.com/6cb050470520e652eeb894fd01f87ca6a2d6034a/content/test/gpu/gpu_tests/webgl_conformance_expectations.py

Labels: -Pri-1 Pri-2
Status: Fixed (was: Assigned)
Closing this, the general failures are tracked in another bug.

Sign in to add a comment