Bug 84786

Summary: [BSW]Piglit spec_glsl-1.50_execution_vs-gs-arrays-within-blocks-pass fails
Product: Mesa Reporter: lu hua <huax.lu>
Component: Drivers/DRI/i965Assignee: Ian Romanick <idr>
Status: VERIFIED DUPLICATE QA Contact: Intel 3D Bugs Mailing List <intel-3d-bugs>
Severity: normal    
Priority: medium CC: ben
Version: unspecified   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description lu hua 2014-10-08 06:53:24 UTC 
System Environment:
--------------------------
Platform: BSW
Libdrm:	(master)libdrm-2.4.58-4-g00847fa48b83a85b0cb882594a12ed1511f780db
Mesa:	(master)16b53005a7df4249fecb6641af0934c32181fdea
Xserver:(master)xorg-server-1.16.0-386-g95a5b92e37f73f497d547fd91c543c16d2cc73de
Xf86_video_intel:(master)2.99.916-84-gec2b9ac81aed0d2dda2948171ca1c260184bf221
Libva:		(master)cdf8636d5fc5b1558570fede347e1599e0d6af3d
Libva_intel_driver:(master)f11176415ec26eb5960ba6841d2d9c22f2cabc60
Kernel:   (drm-intel-nightly)eabc0c8db15f9ba4d727aee5e0612a68cafe1ab5

Bug detailed description:
---------------------------
It fails on BSW with mesa master branch, works well on BDW.

output:
Probe color at (0,0)
  Expected: 0.000000 1.000000 0.000000 1.000000
  Observed: 0.000000 0.000000 0.000000 0.000000
PIGLIT: {"result": "fail" }

Reproduce steps:
-------------------------
1. xinit
2. bin/shader_runner tests/spec/glsl-1.50/execution/vs-gs-arrays-within-blocks-pass.shader_test -auto
Comment 1 Ben Widawsky 2014-11-20 22:24:43 UTC 

*** This bug has been marked as a duplicate of bug 84788 ***
Comment 2 Ben Widawsky 2014-11-20 22:26:32 UTC 

*** This bug has been marked as a duplicate of bug 84777 ***
Comment 3 lu hua 2014-12-16 05:39:49 UTC 
Verified.Fixed.
root@x-bsw01:/GFX/Test/Piglit/piglit# bin/shader_runner tests/spec/glsl-1.50/execution/vs-gs-arrays-within-blocks-pass.shader_test -auto
libGL: OpenDriver: trying /opt/X11R7/lib/dri/tls/i965_dri.so
libGL: OpenDriver: trying /opt/X11R7/lib/dri/i965_dri.so
PIGLIT: {"result": "pass" }

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.