at some point, the following test became intermittent on g965: piglit.spec.ext_framebuffer_multisample.accuracy all_samples srgb depthstencil linear.g965m64 (from piglit) Failing for the past 1 build (Since Unstable#328562 ) Took 0.43 sec. Standard Output /tmp/build_root/m64/lib/piglit/bin/ext_framebuffer_multisample-accuracy all_samples srgb depthstencil linear -auto -fbo Pixels that should be unlit count = 236444 RMS error = 0.025355 Pixels that should be totally lit count = 13308 Perfect output The error threshold for unlit and totally lit pixels test is 0.016650 Pixels that should be partially lit count = 12392 RMS error = 0.273876 The error threshold for partially lit pixels is 0.333000 Samples = 0, Result = fail Because it is intermittent, I don't have a bisection. This bug will be NEEDSINFO until that is available.
I saw that. This is really bizarre. We don't support multisampling prior to Sandybridge, so all of these tests should simply skip. It might be worth running the test with valgrind...
(In reply to Kenneth Graunke from comment #1) The output shows that it is only running with samples=0 so it makes sense that it is running on g965 even though it doesn't have multisample support. I ran it on my HSW with Valgrind and it didn't say anything interesting.
possibly related: https://bugs.freedesktop.org/show_bug.cgi?id=93355 I have also seen occasional SNB gpu hangs due to this test.
This test was skipping before piglit commit f8b7ea69398b4b3d0aaa3e36f864fb22a880e17f.
test seems to pass now
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.