Makes sense, we've had cases where negative test passes because
something else failed;
Reviewed-by: Tapani Pälli
On 11/10/2015 04:49 AM, Timothy Arceri wrote:
From: Timothy Arceri
This makes it much easier to be sure the tests you are writting/running
are failing for the correct reason.
Th
Here's my idea.
We add ubo-fuzzer as a profile. We generate each test file on demand, and
write it out to a temporary file before running it. Then if the test fails
we can record the test into the results file for the developer to come back
and look at later to decide if it's worth keeping. Does t
From: Timothy Arceri
This makes it much easier to be sure the tests you are writting/running
are failing for the correct reason.
This also matches the behaviour of the glslparsertest tool.
---
tests/shaders/shader_runner.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tests/shaders/shad
On 11/09/2015 05:19 AM, Ilia Mirkin wrote:
> On Thu, Sep 25, 2014 at 4:39 PM, Ian Romanick wrote:
>> On 09/24/2014 09:47 AM, Ian Romanick wrote:
>>> So, here it is. Finally.
>>>
>>> The first two patches provide the infrastructure for generating
>>> randomized UBO tests. I think these are pretty
ping?
signature.asc
Description: PGP signature
___
Piglit mailing list
Piglit@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/piglit
From: Dylan Baker
Commit 355090ec0ca8 fixed the glslparsertest and glslparsertest_gles2
binaries to handle gles 3.1+ correctly. This is a follow up series to
fix the python layer to select the correct binary, both for gles 3.1+
and for gl vs gles in different build configurations.
Dylan Baker (3
From: Dylan Baker
This adds a new environment variable, PIGLIT_FORCE_GLSLPARSER_DESKTOP,
which forces glsl_parser_test.py to use "glslparsertest" for GLES tests
(instead of "glslparsertest_gles2").
This could be used to force testing ES__compatibility extensions
even when OpenGL ES tests are bei
From: Dylan Baker
There are two versions of glslparsertest, an undecorated one for desktop
OpenGL, and a '_gles2' suffixed one for OpenGL ES. Piglit should pass 3.1
and 3.2 to the '_gles2' version like it does for GLES 2 and GLES 3.0
This also extends the test generator to cover these new cases
From: Dylan Baker
This patch fixes the behavior of glsl_parser_test in cases other that
OpenGL and OpenGL ES are available. This means that if OpenGL ES isn't
available then OpenGL ES shaders will be passed to the regular version
of glslparsertest, which can run them with an ARB_ES_compatibility
From: Dylan Baker
There are two versions of glslparsertest, an undecorated one for desktop
OpenGL, and a '_gles2' suffixed one for OpenGL ES. Piglit should pass 3.1
and 3.2 to the '_gles2' version like it does for GLES 2 and GLES 3.0
This also extends the test generator to cover these new cases
I confirm that not piglit regression.
-Original Message-
From: Piglit [mailto:piglit-boun...@lists.freedesktop.org] On Behalf Of Eduardo
Lima Mitev
Sent: Thursday, September 10, 2015 11:44 AM
To: piglit@lists.freedesktop.org
Subject: Re: [Piglit] [PATCH] aa: too sensitive at the line end
Why don't we make a ubo-fuzzing profile that Sandra the rest as part of the
output? If be happy to do that if others think it's useful
On Nov 9, 2015 05:19, "Ilia Mirkin" wrote:
> On Thu, Sep 25, 2014 at 4:39 PM, Ian Romanick wrote:
> > On 09/24/2014 09:47 AM, Ian Romanick wrote:
> >> So, here i
On Thu, Sep 25, 2014 at 4:39 PM, Ian Romanick wrote:
> On 09/24/2014 09:47 AM, Ian Romanick wrote:
>> So, here it is. Finally.
>>
>> The first two patches provide the infrastructure for generating
>> randomized UBO tests. I think these are pretty solid, but there are
>> probably ways to impove t
13 matches
Mail list logo
