[Piglit] [PATCH 14/15] framework: Use shader_test.py to drive shader tests

Chad Versace chad.versace at linux.intel.com
Tue Dec 11 15:50:54 PST 2012

On 12/11/2012 04:08 PM, Eric Anholt wrote:
> Chad Versace <chad.versace at linux.intel.com> writes:
>> Add a new class to shader_test.py, ShaderTest. ShaderTest.run() parses the
>> [require] block of the shader test to determine which shader_runner
>> executable should be used to run the test.
>> This is needed because GLES3 shader tests must be run by
>> shader_runner_gles3 and the GL tests by shader_runner.
> I had reviewed up until I hit this patch and... wow.
> How hard would it be to just do piglit-dispatch instead?


Paul and I have occasionally discussed how to approach GLES piglit-dispatch
during the last several weeks. In some aspects, piglit-dispatch
for GLES will be more difficult than the original piglit-dispatch.
Khronos doesn't provide spec files for the GLES API, as it does for
GL. We will have to painstakingly write, or generate, our own.

In short, we need gles3 shader_runner soon. But GLES piglit-dispatch
is at least a man-month of work.

More information about the Piglit mailing list