Bug 91301 - [HSW] intermittant failure of piglit test spec@arb_gpu_shader5@arb_gpu_shader5-emitstreamvertex_nodraw
Summary: [HSW] intermittant failure of piglit test spec@arb_gpu_shader5@arb_gpu_shader...
Status: RESOLVED DUPLICATE of bug 96907
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: Other Linux (All)
: medium normal
Assignee: Ian Romanick
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-10 21:37 UTC by Dylan Baker
Modified: 2016-07-12 20:12 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
piglit results for a failure (4.52 KB, text/plain)
2015-07-10 21:37 UTC, Dylan Baker
Details
piglit results for pass (4.38 KB, text/plain)
2015-07-10 21:37 UTC, Dylan Baker
Details
working failure (4.52 KB, application/octet-stream)
2015-07-10 21:40 UTC, Dylan Baker
Details
working pass (4.38 KB, application/octet-stream)
2015-07-10 21:40 UTC, Dylan Baker
Details

Description Dylan Baker 2015-07-10 21:37:25 UTC
Created attachment 117044 [details]
piglit results for a failure

This test fails or passes randomly. attached are piglit results from both statuses
Comment 1 Dylan Baker 2015-07-10 21:37:50 UTC
Created attachment 117045 [details]
piglit results for pass
Comment 2 Dylan Baker 2015-07-10 21:40:14 UTC
Created attachment 117046 [details]
working failure
Comment 3 Dylan Baker 2015-07-10 21:40:35 UTC
Created attachment 117047 [details]
working pass
Comment 4 Antia Puentes 2015-09-15 09:35:27 UTC
I was unable to reproduce this issue in my HSW laptop using git master a26e82b81dc3cebf13c8fd418d87977f2ab2dbb5 . As it is said in the summary that it is an intermittent failure I executed the tests a considerable amount of times, 1000 times, all of them were a pass.

Is this already fixed?

Thanks.
Comment 5 Mark Janes 2016-07-12 20:12:53 UTC

*** This bug has been marked as a duplicate of bug 96907 ***


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.