This tests regressed with mesa 7bd5931cc1e1102e0171ca70bd2d6bbad81f71dc i965/tex: Unify the TexImage and TexSubImage code It's nearly the same so there's no good reason why it can't be in a common function. The one difference is that _mesa_store_teximage calls AllocTextureImageBuffer for us, while _mesa_store_texsubimage doesn't, but we don't need that anyway - intelTexImage already does it. /tmp/build_root/m32/lib/piglit/bin/shader_runner /tmp/build_root/m32/lib/piglit/tests/spec/arb_shader_bit_encoding/execution/and-clamp.shader_test -auto -fbo Probe color at (2,2) Expected: 0.000000 0.250000 0.500000 -8419755093756528250825501076094976.000000 Observed: 0.000000 0.250980 0.501961 0.000000 Test failure on line 43
That makes no sense, those tests don't call TexImage or TexSubImage at all. They pass for me on that commit on Kabylake.
-8419755093756528250825501076094976.000000 makes no sense as an expected value either. This smells like a Piglit bug in shader_runner.
Should be fixed by Piglit commit: commit 3093326348b632ce9a9b92b9289725c400aa77b0 Author: Kenneth Graunke <kenneth@whitecape.org> Date: Mon Sep 18 14:15:38 2017 -0700 Fix bogus .50. number in and-clamp.shader_test Trivial. ".50." is clearly a typo, it should have been ".50" This fixes test failures in some environments. Tested-by: Mark Janes <mark.a.janes@intel.com>
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.