Bug 107470

Summary:	2 of 5 piglit sanity tests fail (ppc64, big endian)
Product:	piglit	Reporter:	erhard_f
Component:	tests	Assignee:	Piglit Mailing List <piglit>
Status:	RESOLVED INVALID	QA Contact:	Piglit Mailing List <piglit>
Severity:	normal
Priority:	medium	Keywords:	regression
Version:	unspecified
Hardware:	PowerPC
OS:	All
See Also:	https://bugs.freedesktop.org/show_bug.cgi?id=107448 https://bugs.freedesktop.org/show_bug.cgi?id=105463
Whiteboard:
i915 platform:		i915 features:

Description erhard_f 2018-08-03 13:05:01 UTC

Built piglit from git-master (67675034486e29ecbc4a4da2fc74b184d7d11cb8) and wanted to run the testsuite on my PowerMac G5 + Radeon HD 6450 (ppc64, big endian). However 2 sanity tests fail (with mesa 18.1.5 and mesa 18.0.5). This might be a regression in piglit, 'cause piglit passed sanity tests on the same system at the time mesa 18.0.0 was released.

For more info see bug #107448.


Command
/root/build/piglit/bin/shader_runner /root/build/piglit/test/spec/arb_tessellation_shader/execution/sanity.shader_test -auto -fbo

Stdout 	
Probe color at (0,0)
  Expected: 0 255 0 255
  Observed: 25 25 25 25
Test failure on line 57

Stderr 	
Mesa: User error: GL_INVALID_ENUM in lGetFramebufferAttachmentParameteriv(invalid attachment GL_NONE)


Command
/root/build/piglit/bin/glsl-1.50-transform-feedback-builtins -auto -fbo

Stdout 	
Incorrect data for 'gl_Layer' output 0.  Expected 1, got 16777216.
Incorrect data for 'gl_Layer' output 1.  Expected 3, got 50331648.
Incorrect data for 'gl_Layer' output 2.  Expected 5, got 83886080.
Incorrect data for 'gl_ViewportIndex' output 0.  Expected 1, got 16777216.
Incorrect data for 'gl_ViewportIndex' output 1.  Expected 2, got 33554432.
Incorrect data for 'gl_ViewportIndex' output 2.  Expected 3, got 50331648.

Comment 1 Adam Jackson 2019-03-06 15:32:18 UTC

Failing sanity is almost certainly a driver bug, not a piglit bug.

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.