[Bug 96907] piglit.spec.arb_gpu_shader5.arb_gpu_shader5-emitstreamvertex_nodraw intermittent

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96907

Mark Janes <mark.a.janes at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|idr at freedesktop.org         |kenneth at whitecape.org

--- Comment #1 from Mark Janes <mark.a.janes at intel.com> ---
Ken, please verify my bisection before spending too much time on this.  It was
difficult and time consuming to reproduce.  I was able to trigger the test
failure by running the test in a loop, while simultaneously running a full
piglit suite in another window.  Here are the ways I invoked the two workloads:

for ((;;)) do
/tmp/build_root/m64/lib/piglit/bin/arb_gpu_shader5-emitstreamvertex_nodraw
-auto -fbo; done

and 

piglit run -o -p gbm --exclude-tests timestamp-get --exclude-tests glsl-routing
--exclude-tests ext_timer_query --exclude-tests arb_timer_query --exclude-tests
spec.khr_debug.object-label_gl --exclude-tests
arb_framebuffer_no_attachments.arb_framebuffer_no_attachments-atomic
--exclude-tests vs-float-main-return --config
/home/jenkins/workspace/Leeroy/piglit-test//ivb.conf --exclude-tests
glsl-1.10.execution.vs-vec2-main-return --exclude-tests
spec.egl.1.4.eglquerysurface.egl --exclude-tests
spec.egl.ext.client.extensions.conformance --exclude-tests
spec.egl.khr.create.context --exclude-tests spec.egl.khr.get.all.proc.addresses
--exclude-tests spec.egl.khr.surfaceless.context --exclude-tests
spec.egl.mesa.configless.context --exclude-tests spec.egl.nok.swap.region
--exclude-tests spec.egl.nok.texture.from.pixmap.basic --exclude-tests
spec.egl.1.4.eglterminate.then.unbind.context --exclude-tests
spec.egl.chromium.sync.control.conformance --exclude-tests
arb.shader.image.load.store.execution.coherency-extra --exclude-tests
arb.separate.shader.objects.validateprogrampipeline --exclude-tests
glsl-1.50.execution.geometry.clip-distance --exclude-tests
glsl-1.50.execution.gs-redeclares-pervertex-out-only --exclude-tests
glsl-1.50.execution.redeclare-pervertex-subset-vs-to-gs --exclude-tests
glsl-1.50.transform-feedback-type-and-size --exclude-tests
arb.sync.clientwaitsync-timeout --exclude-tests
arb.compute.shader.zero-dispatch-size -c gpu /tmp/build_root/m64/test/ivbgt2


In my tests, the looping test generally failed while the first few hundred
tests in the piglit suite were executing.  Occasionally, I would have to
restart the piglit suite to produce the failure.  Also, the looping test failed
around test 4000 more than once.

I spent several iterations confirming that the looping test failed at the
bisected revision, and I could never make it fail on the previous revision.

This failure mode has been seen on IVBGT2 and BXT.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20160712/13b98eae/attachment.html>