lodbias: increase window size to fix test on Windows

Before, the 96x96 window got bumped up to 116x96 by Windows and we
saw a "Got spurious window resize in automatic run" message and the
test reported "warn".

Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
arb_sampler_objects: use default window size to fix Windows run

Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
arb_shader_objects: use default window size to fix Windows run

Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
arb_framebuffer_object: use default window size to fix Windows run

Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
arb_vertex_buffer_object: use default window size to fix Windows run

Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
gl-1.0: use default window size to fix Windows run

Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
draw-pixels: whitespace fixes, remove unneeded parenthesis

Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
draw-pixels: display results when there's a failure

Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
draw-pixels: use better test values

As it was, many of the generated / expected pixel values were all
zeros.  Use better values that actually fit in the given datatype.

For example, we were trying to store "0x23 << (6 - j)" in a GLbyte.

Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
draw-pixels: use default window size, for Windows

And set the pixel unpack alignment to 1 so that we don't fail if
the window width isn't a multiple of four.

Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
Test that transform feedback works with non-flat integers.

Commit 0fac0a6 (Modify tests for error checking on "flat" keyword to
match updated specs) adopted the GLSL 1.50 rules for "flat" varyings
for all desktop GL tests (the rationale was that this change likely
reflects a bug fix rather than a deliberate behavioural difference).

The GLSL 1.50 rules allow a vertex shader output to be a non-flat
integer provided that it isn't consumed by the fragment shader.  In
particular, this means that a non-flat integer may be used with
transform feedback.

This test verifies that transform feedback works correctly for all
integral types, even if they are not declared as "flat".

Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
glsl-es-1.00: sanity.shader_test fragment needs default precision

GLSL ES 1.00 spec 4.5.3 page 36:
"The fragment language has no default precision qualifier for
floating point types."

Adding default precision for float in the fragment shader
so this sanity testcase doesn't error out.
mediump is choosen since according to 4.5.2 page 34:
"The fragment language requires any uses of lowp and mediump to
compile without error.  Support for highp is optional."

Signed-off-by: Tom Gall <tom.gall@linaro.org>
Reviewed-by: Stuart Abercrombie <sabercrombie@chromium.org>
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
new test: glsl-fs-uniform-array-loop-unroll.shader_test

In a loop, access past the end of a uniform array, to check
if stages after loop unrolling can handle the bad access.

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

Signed-off-by: Frank Henigman <fjhenigman@google.com>
Reviewed-by: Eric Anholt <eric@anholt.net>
Test interaction of primitive restart and transform feedback.

v2: Fix "written" subtest (which was testing the wrong query).

Reviewed-by: Eric Anholt <eric@anholt.net>
gtf: Update arguments for current GLES conformance from upstream.

They switched the default for imagefileio, so they renamed the option
(while leaving out support for the old option, making our tests fail).
This happened some time between our last ES2 drop, and ES3.  Since the
current stuff still contains all the ES2 tests, we don't need support
for the old version.

Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
gtf: Parse either the old or new GLES conformance suite output.

Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
glsl-1.30: add test for default in switch not after all case statements

By the looks of it "default" is not required to appear as last statement
in a switch expression, and c rules should be followed (which is probably
a mess to implement thanks to fallthrough).
Seems to fail with mesa glsl compiler (at least with tgsi translation).

Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
Reviewed-by: Eric Anholt <eric@anholt.net>
cl: Fix Windows build.

Fixes two trivial issues:

- on Windows large integers like 0xff000001 are not `int` objects, but
  rather `long` objects, so accept both types.

- and the error message caused exception

   TypeError: cannot concatenate 'str' and 'long' objects
Rework the PIGLIT_GL_VISUAL flags, fix RGB vs RGBA vs ALPHA confusion

Changes:
- SINGLE is removed, because its value was 0
- ALPHA is removed, because it becomes redundant with this change
- RGB asks for an RGB visual
- RGBA asks for an RGBA visual
- if RGB and RGBA are unset, it asks for a visual without RGB(A)

Reviewed-by: Brian Paul <brianp@vmware.com>
Reviewed-by: Chris Forbes <chrisf@ijw.co.nz>
Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>

v2: fix glut
framework: Fix "inconsistent use of tabs and spaces in indentation" warnings.

These warnings have become fatal errors in Python 3.x.

Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>