AMD_vertex_shader_layer: add layered-2d-texture-render test

This tests the AMD_vertex_shader_layer extension using a
color 2D array texture.

Signed-off-by: Jordan Justen <jordan.l.justen@intel.com>
Reviewed-by: Matt Turner <mattst88@gmail.com>
AMD_vertex_shader_layer: Add depth render test

This tests layered depth rendering in the vertex shader.

Signed-off-by: Jordan Justen <jordan.l.justen@intel.com>
Reviewed-by: Matt Turner <mattst88@gmail.com>
glsl-1.50: test for interface block global name reuse error

Placing the use of the block name before the block declaration currently
compiles with Mesa, which is a bug.

Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
gen_dispatch.py: Use PIGLIT_DISPATCH_ES1.

No dispatch for ES1 implemented, but we should at least be consistent
with piglit-dispatch.*.

Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
egl_khr_create_context: Remove printf to avoid piglit warning.

Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
egl_khr_create_context: Use PIGLIT_DISPATCH_ES* when possible.

Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
egl_khr_create_context: Build ES tests only when ES 1 and ES 2 are available.

This was, and still is, kind of broken. Previously we were building ES
tests without linking to libGLES* which lead to the tests being skipped.

Now we're requiring ES 2 for tests that can run with ES 1 or ES 2; or
ES 1, ES 2, or Desktop GL. There is potential for build problems if
building with ES 2 but without ES 1 or Desktop GL.

tests/egl/spec/egl_khr_create_context must have CMakeLists.gles2.txt
(as opposed to CMakeLists.gles1.txt) since piglit dispatch isn't
implemented for ES 1, and we need dispatch.

Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
generate-glean-tests.py: PEP8 compliance

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
piglit-merge-results.py: PEP8 compliance

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
piglit-print-commands.py: PEP8 compliance

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
piglit-run.py: PEP8 Compliance

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
piglit-summary-html.py: PEP8 Compliance

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
piglit-summary.py: PEP8 compliance

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
core.py: PEP8 Compliance

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
exectest.py: PEP8 compliance

v3: - revert some changes that were false positives from on old version
      of the pep8 tool

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
gleantest.py: PEP8 compliance

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
glsl_parser_test.py: Remove bad vim modeset line

Removes a vim modeset line that is not PEP8 compliant

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
glsl_parser_test.py: PEP8 compliance

There is one non-compliance, a docstring comment that is longer than 79
characters. However, this is a comment for a c-style file, and there is
no way to break it without changing its meaning.

v2: Revert one change to previous PEP8 compliant implementation

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
log.py: PEP8 compliance

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
patterns.py: PEP8 compliance

There are four lines in a docstring that are not compliant, they are c++
code, and as such should not be wrapped.

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>