| Summary: | [i965]Piglit shaders_glsl-deriv-varyings fails on Mesa 10.4 | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | lu hua <huax.lu> |
| Component: | Drivers/DRI/i965 | Assignee: | Ian Romanick <idr> |
| Status: | RESOLVED FIXED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
| Severity: | normal | ||
| Priority: | high | CC: | agomez, idr, mattst88 |
| Version: | 10.4 | ||
| Hardware: | All | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
lu hua
2014-12-17 03:23:05 UTC
As the patch's description, it only exposes Mesa issue. Reset to Mesa. There's already a bug for this... it's mentioned in the commit message that you quoted. *** This bug has been marked as a duplicate of bug 82991 *** bug 82991 fixed. but this case still fails on the latest mesa 10.6 branch. libGL: OpenDriver: trying /opt/X11R7/lib/dri/tls/i965_dri.so libGL: OpenDriver: trying /opt/X11R7/lib/dri/i965_dri.so libGL: Using DRI2 for screen 0 Probe color at (355,125) Expected: 0.800000 0.400000 0.000000 Observed: 0.800000 0.000000 0.000000 PIGLIT: {"result": "fail" } (In reply to lu hua from comment #3) > bug 82991 fixed. but this case still fails on the latest mesa 10.6 branch. > libGL: OpenDriver: trying /opt/X11R7/lib/dri/tls/i965_dri.so > libGL: OpenDriver: trying /opt/X11R7/lib/dri/i965_dri.so > libGL: Using DRI2 for screen 0 > Probe color at (355,125) > Expected: 0.800000 0.400000 0.000000 > Observed: 0.800000 0.000000 0.000000 > PIGLIT: {"result": "fail" } Is this failure happening with latest piglit? Notice that the test was modified as a result of fixing bug 87407. (In reply to Andrés Gómez García from comment #4) > (In reply to lu hua from comment #3) > > bug 82991 fixed. but this case still fails on the latest mesa 10.6 branch. > > libGL: OpenDriver: trying /opt/X11R7/lib/dri/tls/i965_dri.so > > libGL: OpenDriver: trying /opt/X11R7/lib/dri/i965_dri.so > > libGL: Using DRI2 for screen 0 > > Probe color at (355,125) > > Expected: 0.800000 0.400000 0.000000 > > Observed: 0.800000 0.000000 0.000000 > > PIGLIT: {"result": "fail" } > > Is this failure happening with latest piglit? Notice that the test was > modified as a result of fixing bug 87407. That is correct, that test does not exist any more in piglit, it has been replaced by these other tests: bin/shader_runner ./tests/shaders/glsl-derivs-sign.shader_test -auto bin/shader_runner ./tests/shaders/glsl-derivs-varyings.shader_test -auto bin/shader_runner ./tests/shaders/glsl-derivs-abs-sign.shader_test -auto bin/shader_runner ./tests/shaders/glsl-derivs-abs.shader_test -auto bin/shader_runner ./tests/shaders/glsl-derivs-swizzle.shader_test -auto All of which pass fine for me. Lu, you probably still have the binary for the old program and that is why you did not notice. I think this can be closed again. Christophe, Does this issue still happen on your machines? (In reply to Andrés Gómez García from comment #4) > (In reply to lu hua from comment #3) > > bug 82991 fixed. but this case still fails on the latest mesa 10.6 branch. > > libGL: OpenDriver: trying /opt/X11R7/lib/dri/tls/i965_dri.so > > libGL: OpenDriver: trying /opt/X11R7/lib/dri/i965_dri.so > > libGL: Using DRI2 for screen 0 > > Probe color at (355,125) > > Expected: 0.800000 0.400000 0.000000 > > Observed: 0.800000 0.000000 0.000000 > > PIGLIT: {"result": "fail" } > > Is this failure happening with latest piglit? Notice that the test was > modified as a result of fixing bug 87407. Just now, compiled mesa 10.6 branch and passed the tests with piglit's master: $ for i in ./tests/shaders/glsl-derivs-*; do echo $i; ./bin/shader_runner $i -auto -fbo; done ./tests/shaders/glsl-derivs-abs.shader_test PIGLIT: {"result": "pass" } ./tests/shaders/glsl-derivs-abs-sign.shader_test PIGLIT: {"result": "pass" } ./tests/shaders/glsl-derivs-sign.shader_test PIGLIT: {"result": "pass" } ./tests/shaders/glsl-derivs-swizzle.shader_test PIGLIT: {"result": "pass" } ./tests/shaders/glsl-derivs-varyings.shader_test PIGLIT: {"result": "pass" } |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.