WebglConformance_conformance2_extensions_ext_color_buffer_float failure on Linux Intel |
|||
Issue descriptionFailing on https://build.chromium.org/p/chromium.gpu.fyi/builders/Linux%20Release%20%28New%20Intel%29?numbuilds=200 with Traceback (most recent call last): _RunGpuTest at content/test/gpu/gpu_tests/gpu_integration_test.py:71 self.RunActualGpuTest(url, *args) RunActualGpuTest at content/test/gpu/gpu_tests/webgl_conformance_integration_test.py:50 self.fail(webgl_conformance._WebGLTestMessages(self.tab)) fail at /usr/lib/python2.7/unittest/case.py:410 raise self.failureException(msg) AssertionError: floating-point RGBA32F render target not supported FAIL floating-point RGBA32F render target not supported
,
Aug 23 2016
Jie, this bug has been fixed in ToT Intel mesa driver, right?
,
Aug 24 2016
It seems to be irrelevant to intel mesa driver version. The error is not reproducible from chromium browser. I will try to reproduce from gpu_tests.
,
Aug 24 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/284c15c86d9d9cd9e0e7cdbcb71c70edc74fbd4c commit 284c15c86d9d9cd9e0e7cdbcb71c70edc74fbd4c Author: vmpstr <vmpstr@chromium.org> Date: Wed Aug 24 01:47:14 2016 gpu tests: Suppress failing ext-color-buffer-float test on linux intel. BUG=640389 TBR=kbr@chromium.org 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/2267343003 Cr-Commit-Position: refs/heads/master@{#413932} [modify] https://crrev.com/284c15c86d9d9cd9e0e7cdbcb71c70edc74fbd4c/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py
,
Aug 24 2016
Failed to run content/test/gpu/gpu_tests/gpu_integration_test.py. Likely I might have missed some setup steps to run gpu_tests. Is there any guide that I can refer to? Besides may I know the chrome://gpu info of this bot? So that I may be able to find a similar device to investigate. From my side, it's not reproducible on my gpu(Mesa DRI Intel(R) Iris Pro 6200 (Broadwell GT3e)) with both the default ubuntu driver(3.3 (Core Profile) Mesa 11.2.0) and ToT mesa driver(4.4 (Core Profile) Mesa 12.1.0-devel).
,
Aug 25 2016
If you build Chromium in Release mode then running: ./content/test/gpu/run_gpu_integration_test.py webgl_conformance --browser=release will run the WebGL 1.0 tests. ./content/test/gpu/run_gpu_integration_test.py webgl_conformance --webgl-conformance-version=2.0.0 --browser=release will run the WebGL 2.0 tests. ./content/test/gpu/run_gpu_integration_test.py webgl_conformance --webgl-conformance-version=2.0.0 --browser=release --test-filter=conformance2_extensions lets you run a subset of the tests. Some more documentation is at https://www.chromium.org/developers/testing/gpu-testing#TOC-Running-the-GPU-Tests-Locally but it might not all be relevant or up to date.
,
Aug 25 2016
Thanks for helping. It has worked. But I failed to reproduce the "FAIL floating-point RGBA32F render target not supported" error". Without the ToT mesa driver, the error has been "FAIL the maximum value in SAMPLES should be at least 8" on my Ubuntu 16.04 BroadWell machine. Anyway let's wait for the TOT mesa driver.
,
Jun 20 2017
,
Aug 23
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/d894e4818670624d52b6ae3122e08eddad14dcbe commit d894e4818670624d52b6ae3122e08eddad14dcbe Author: jchen10 <jie.a.chen@intel.com> Date: Thu Aug 23 06:44:37 2018 Whitelist ext-color-buffer-float conformance test Remove the it from the expectation. Bug: 640389 Change-Id: Id90ed5c40069fe36710782fe440b385a2b1e69e3 Reviewed-on: https://chromium-review.googlesource.com/1174102 Reviewed-by: Kenneth Russell <kbr@chromium.org> Commit-Queue: Jie A Chen <jie.a.chen@intel.com> Cr-Commit-Position: refs/heads/master@{#585416} [modify] https://crrev.com/d894e4818670624d52b6ae3122e08eddad14dcbe/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py |
|||
►
Sign in to add a comment |
|||
Comment 1 by kbr@chromium.org
, Aug 23 2016