Dylan, looks like with your latest json-ification changes:
$ bin/arb_viewport_array-bounds -fbo -auto
Mesa: User error: GL_INVALID_VALUE in glViewportArrayv: index (0)
width or height 0 (-10.30, 0.00)
Mesa: User error: GL_INVALID_VALUE in glViewportIndexedf: index (1)
width or height 0
This test demonstrates a bug in which PiglitTest clobbers subtest
results.
Signed-off-by: Dylan Baker baker.dyla...@gmail.com
---
framework/tests/exectest_test.py | 15 +++
1 file changed, 15 insertions(+)
diff --git a/framework/tests/exectest_test.py
This method is used during PiglitTest.interpret_result() to update
subtest entries safely. I chose this approach since it is robust,
reusable, and it felt more natural as a part of TestResult than putting
it in PiglitTest.interpret_result()
Signed-off-by: Dylan Baker baker.dyla...@gmail.com
---
On Wed, Jul 2, 2014 at 4:02 AM, Dylan Baker baker.dyla...@gmail.com wrote:
This method is used during PiglitTest.interpret_result() to update
subtest entries safely. I chose this approach since it is robust,
reusable, and it felt more natural as a part of TestResult than putting
it in
Oops, that's what I get for writing and sending a patch at 1AM
On Wednesday, July 02, 2014 10:36:53 AM Ilia Mirkin wrote:
On Wed, Jul 2, 2014 at 4:02 AM, Dylan Baker baker.dyla...@gmail.com wrote:
This method is used during PiglitTest.interpret_result() to update
subtest entries safely. I
This method is used during PiglitTest.interpret_result() to update
subtest entries safely. I chose this approach since it is robust,
reusable, and it felt more natural as a part of TestResult than putting
it in PiglitTest.interpret_result()
v2: - Fix commit message
Signed-off-by: Dylan Baker
This test demonstrates a bug in which PiglitTest clobbers subtest
results.
Signed-off-by: Dylan Baker baker.dyla...@gmail.com
---
framework/tests/exectest_test.py | 15 +++
1 file changed, 15 insertions(+)
diff --git a/framework/tests/exectest_test.py
On Wed, Jul 2, 2014 at 1:17 PM, Dylan Baker baker.dyla...@gmail.com wrote:
This method is used during PiglitTest.interpret_result() to update
subtest entries safely. I chose this approach since it is robust,
reusable, and it felt more natural as a part of TestResult than putting
it in
This is a copy of the render_viewport ARB_viewport_array test. I didn't
think that it was worth it to copy the scissor/depth tests, since they
basically test the same thing but making sure that scissor/depth are
applied correctly. If that works for ARB_viewport_array, it really
should work here
On Wednesday, July 02, 2014 10:39:57 AM Dylan Baker wrote:
On Wednesday, July 02, 2014 01:28:09 PM Ilia Mirkin wrote:
On Wed, Jul 2, 2014 at 1:17 PM, Dylan Baker baker.dyla...@gmail.com
wrote:
This method is used during PiglitTest.interpret_result() to update
subtest entries safely. I
---
generated_tests/generate-cl-math-builtins.py | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/generated_tests/generate-cl-math-builtins.py
b/generated_tests/generate-cl-math-builtins.py
index edf93da..d93f09f 100644
---
---
generated_tests/genclbuiltins.py | 7 +--
generated_tests/generate-cl-math-builtins.py | 11 +++
tests/cl/program/program-tester.c| 1 -
3 files changed, 16 insertions(+), 3 deletions(-)
diff --git a/generated_tests/genclbuiltins.py
This doesn't need to remain in the GL-specific utility library.
Signed-off-by: Josh Triplett j...@joshtriplett.org
---
tests/util/piglit-util-gl-common.c | 102 +
tests/util/piglit-util-gl.c| 102 -
2 files changed,
13 matches
Mail list logo