Please apply. Initially posted ~ a month ago. No negative feedback.
From tests/spec/glsl-1.10 extend variable-index-read.sh so that
it can also correctly generates variable index read tests that
support glsl-es-1.00.
1.00 added as a valid parameter to generated tests for glsl-es-1.00.
For 1.00
Please apply. Initially posted ~ a month ago. No negative feedback.
From tests/spec/glsl-1.10 extend variable-index-write.sh so that
it can also correctly generates variable index write tests that
support glsl-es-1.00.
1.00 added as a valid parameter to generated tests for glsl-es-1.00.
For
On 17 April 2013 09:54, Paul Berry stereotype...@gmail.com wrote:
On 17 April 2013 07:37, Brian Paul bri...@vmware.com wrote:
On 04/17/2013 03:48 AM, Kenneth Graunke wrote:
Does anyone object to porting to Python 3.x (and dropping 2.x support)?
Some useful data points:
- Debian stable has
Normally, if anything unexpected is printed to stderr we report 'warn'
for the test result. The list of expected/allowed stderr message is
found at the end of core.py. It's a PITA to update this list and if
you've temporarily inserted extra debug code in Mesa/gallium it causes
piglit to just
When doing a full piglit run it's helpful to have all the OpenGL
driver version/vendor/extension info. The piglit framework tries
to run glxinfo/wglinfo and include the output in the results file,
but sometimes those programs aren't installed.
---
tests/all.tests |1 +
generated_tests/generate-cl-int-builtins.py in getValue, at the
very end some logic checks for an instance of an int and returns
it.
In the case of a long, this fails and results in a TypeError
killing the build.
Add a check for an instance of a long and return the number just
as is done for an
Bah! Ignore. Didn't realize my repo was slightly out of date. Sorry about that!
On Thu, Apr 18, 2013 at 3:39 PM, Tom Gall tom.g...@linaro.org wrote:
generated_tests/generate-cl-int-builtins.py in getValue, at the
very end some logic checks for an instance of an int and returns
it.
In the
If only one result file is specified, just print all the tests
followed by the outcome. For example:
fbo/FBO blit from missing attachment: pass
fbo/FBO blit to missing attachment: fail
fbo/fbo-1d: pass
fbo/fbo-3d: crash
[...]
If multiple result files are specified, we'll print pass/fail/etc
for
