This test fails intermittently on SNB: /tmp/build_root/m64/lib/piglit/bin/shader_runner /tmp/build_root/m64/lib/piglit/generated_tests/spec/amd_shader_trinary_minmax/execution/built-in-functions/gs-mid3-ivec2-ivec2-ivec2.shader_test -auto piglit: debug: Requested an OpenGL 3.2 Core Context, and received a matching 3.3 context Probe color at (128,4) Expected: 0.000000 1.000000 0.000000 1.000000 Observed: 0.000000 0.000000 1.000000 0.000000 Probe color at (132,4) Expected: 0.000000 1.000000 0.000000 1.000000 Observed: 0.000000 0.000000 1.000000 0.000000 Probe color at (136,4) Expected: 0.000000 1.000000 0.000000 1.000000 Observed: 0.000000 0.000000 1.000000 0.000000 Probe color at (140,4) Expected: 0.000000 1.000000 0.000000 1.000000 Observed: 0.000000 0.000000 1.000000 0.000000 Running it repeatedly on its own does not reproduce the bug. It has been disabled in Intel's CI.
These tests (as do likely all geometry shaders on Sandybridge) spill. Curro thinks that spilling in the vec4 backend is broken, which is a good hypothesis for why these tests fail intermittently when run in CI.
This should be fixed by: commit 0d5ce25c1ca23abc6d91538f4374a18509091060 (origin/master, origin/HEAD) Author: Ian Romanick <ian.d.romanick@intel.com> Date: Mon Apr 16 16:32:41 2018 -0700 intel/compiler: Add scheduler deps for instructions that implicitly read g0 Otherwise the scheduler can move the writes after the reads. Signed-off-by: Ian Romanick <ian.d.romanick@intel.com> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=95009 Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=95012 Reviewed-by: Kenneth Graunke <kenneth@whitecape.org> Reviewed-by: Jason Ekstrand <jason@jlekstrand.net> Tested-by: Mark Janes <mark.a.janes@intel.com> Cc: Clayton A Craft <clayton.a.craft@intel.com> Cc: mesa-stable@lists.freedesktop.org
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.