WebGL test 'glsl/matrices/glsl-mat4-to-mat3' flaky on Windows D3D9 |
|||||
Issue descriptionExample failing build: https://build.chromium.org/p/chromium.gpu.fyi/builders/Win8%20Debug%20%28NVIDIA%29/builds/14223 [ RUN ] WebglConformance.conformance_glsl_matrices_glsl_mat4_to_mat3 (INFO) 2016-06-03 06:27:10,845 cache_temperature.EnsurePageCacheTemperature:55 PageCacheTemperature: any [3108:4076:0603/062711:INFO:CONSOLE(11)] "images are different: at (0,0): ref=(0,0,255,255) test=(4,4,0,255) tolerance=0", source: (11) [3108:4076:0603/062711:INFO:CONSOLE(11)] "FAIL images are different: at (0,0): ref=(0,0,255,255) test=(4,4,0,255) tolerance=0", source: (11) Traceback (most recent call last): File "c:\users\chrome~1\appdata\local\temp\runhjhdx1\third_party\catapult\telemetry\telemetry\internal\story_runner.py", line 84, in _RunStoryAndProcessErrorIfNeeded state.RunStory(results) File "c:\users\chrome~1\appdata\local\temp\runhjhdx1\content\test\gpu\gpu_tests\gpu_test_base.py", line 122, in RunStory RunStoryWithRetries(DesktopGpuSharedPageState, self, results) File "c:\users\chrome~1\appdata\local\temp\runhjhdx1\content\test\gpu\gpu_tests\gpu_test_base.py", line 72, in RunStoryWithRetries super(cls, shared_page_state).RunStory(results) File "c:\users\chrome~1\appdata\local\temp\runhjhdx1\third_party\catapult\telemetry\telemetry\page\shared_page_state.py", line 308, in RunStory self._current_page, self._current_tab, results) File "c:\users\chrome~1\appdata\local\temp\runhjhdx1\content\test\gpu\gpu_tests\webgl_conformance.py", line 87, in ValidateAndMeasurePage raise page_test.Failure(_WebGLTestMessages(tab)) Failure: images are different: at (0,0): ref=(0,0,255,255) test=(4,4,0,255) tolerance=0 FAIL images are different: at (0,0): ref=(0,0,255,255) test=(4,4,0,255) tolerance=0 Only seems to happen on D3D9. This is causing problems with the ANGLE CQ. Going to mark as flaky. cc'ing Eric, current GPU sheriff.
,
Jun 3 2016
Test marked as flaky but not fixed, unassigning myself for now.
,
Jul 24 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/07941713abef60bb042135db521e5df17d88a9c9 commit 07941713abef60bb042135db521e5df17d88a9c9 Author: jmadill <jmadill@chromium.org> Date: Sun Jul 24 00:32:02 2016 WebGL: Update expectations. BUG= 483282 , 594922 , 478572, 630860 , 617148 TBR=zmo@chromium.org NOTRY=true 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 Review-Url: https://codereview.chromium.org/2178803002 Cr-Commit-Position: refs/heads/master@{#407376} [modify] https://crrev.com/07941713abef60bb042135db521e5df17d88a9c9/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py [modify] https://crrev.com/07941713abef60bb042135db521e5df17d88a9c9/content/test/gpu/gpu_tests/webgl_conformance_expectations.py
,
Jun 20 2017
,
Jun 21 2018
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. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 21 2018
The D3D9 backend is not a priority any more. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by bugdroid1@chromium.org
, Jun 3 2016