WebglConformance_conformance2_glsl3_vector_dynamic_indexing_swizzled_lvalue failing on Win7 Release (NVIDIA), Linux Release (AMD R7 240) and Linux Release (Intel HD 530) |
|||
Issue description
Started when the test was added.
[69/2626] gpu_tests.webgl_conformance_integration_test.WebGLConformanceIntegrationTest.WebglConformance_conformance2_glsl3_vector_dynamic_indexing_swizzled_lvalue failed unexpectedly 0.9668s:
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:213
self.fail(self._WebGLTestMessages(self.tab))
fail at /usr/lib/python2.7/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
FAIL should be green
at (0, 0) expected: 0,255,0,255 was 255,0,0,255
Locals:
msg : u'should be green\nat (0, 0) expected: 0,255,0,255 was 255,0,0,255\nFAIL should be green\nat (0, 0) expected: 0,255,0,255 was 255,0,0,255\n'
No path to crashpad_database_util found
No minidump found via crashpad_database_util
No minidump paths to symbolize
No path to crashpad_database_util found
No minidump found via crashpad_database_util
Restarting browser due to unexpected test failure
Starting browser, attempt 1 of 3
,
Apr 10 2017
,
Jun 20 2017
,
Nov 12
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/a5f88b7e35a567c40e25e21b285ec7e8c687e6d6 commit a5f88b7e35a567c40e25e21b285ec7e8c687e6d6 Author: James Darpinian <jdarpinian@chromium.org> Date: Mon Nov 12 23:09:19 2018 Cleaning up WebGL test failure expectations. Many of these are leftover failure expectations from fixed bugs. Some were fixed on some platforms but not others. There are some new failures that were hidden by previous broad suppressions. Also some tests are only failing because we haven't updated the drivers on the bots (http://crbug.com/887241). Bug: 757097 , 838133 , 672380 , 625738, angleproject:2325 Bug: 534697 , 849572, 625738, 703779, angleproject:2142 Bug: 757098, 644740, 705865, 602688, angleproject:2103 Bug: 903903, 740769 , 662644, 680720 , angleproject:1932 Bug: 709874 , 887241, 625365 , angleproject:2952 Change-Id: I4e39e5a09d31d788d8a8615ad06d1ec88f064f00 Reviewed-on: https://chromium-review.googlesource.com/c/1325197 Commit-Queue: James Darpinian <jdarpinian@chromium.org> Reviewed-by: Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#607367} [modify] https://crrev.com/a5f88b7e35a567c40e25e21b285ec7e8c687e6d6/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py [modify] https://crrev.com/a5f88b7e35a567c40e25e21b285ec7e8c687e6d6/content/test/gpu/gpu_tests/webgl_conformance_expectations.py [modify] https://crrev.com/a5f88b7e35a567c40e25e21b285ec7e8c687e6d6/content/test/gpu/gpu_tests/webgl_conformance_expectations_unittest.py |
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Apr 10 2017