Re: [Piglit] [PATCH] Add dmesg option for reboot policy

2015-11-24 Thread Dylan Baker
On Tue, Nov 24, 2015 at 02:10:34PM +, Emil Velikov wrote: > Hi Yan, > > The plan of having such a module is pretty sound. > > That said I think that the actual policy/implementation could use some tweaks. > > On 24 November 2015 at 12:14, wrote: > > From:

Re: [Piglit] [PATCH v4 0/3] Fix glslparsertest python layer for gles 3.1+

2015-11-24 Thread Dylan Baker
On Fri, Nov 20, 2015 at 05:37:10PM -0800, baker.dyla...@gmail.com wrote: > From: Dylan Baker > > Changes from previous version: > - rebase on master > - fix bug in v3 > - small cleanups > > Dylan Baker (3): > glsl_parser_test.py: Fix which versions are sent to >

[Piglit] [PATCH V3] arb_separate_shader_objects: test mixed explicit and non-explicit locations

2015-11-24 Thread Timothy Arceri
From: Timothy Arceri This tests a bug in Mesa where explicit locations are not taken into account when assigning varying locations which results in two inputs/outputs being given the same location. Test results: Nvidia GeForce 840M - NVIDIA 352.41: pass i965 - Mesa

Re: [Piglit] [PATCH 2/6] shader_runner: Don't call glDeleteProgram on an ARB program.

2015-11-24 Thread Kenneth Graunke
On Tuesday, November 24, 2015 02:20:10 PM Matt Turner wrote: > On Wed, Nov 11, 2015 at 4:53 PM, Kenneth Graunke > wrote: > > On Tuesday, November 10, 2015 10:46:19 PM Matt Turner wrote: > >> I don't feel good about this check, but it is done elsewhere in the same > >> file

Re: [Piglit] [PATCH v4] glsl-4.50: add a test for helper invocations

2015-11-24 Thread Matt Turner
On Thu, Nov 12, 2015 at 2:55 PM, Glenn Kennard wrote: > Tested on r600g implementation > > Signed-off-by: Glenn Kennard > --- I used this to test the i965 implementation as well. Please push it. ___

Re: [Piglit] [PATCH 2/6] shader_runner: Don't call glDeleteProgram on an ARB program.

2015-11-24 Thread Matt Turner
On Wed, Nov 11, 2015 at 4:53 PM, Kenneth Graunke wrote: > On Tuesday, November 10, 2015 10:46:19 PM Matt Turner wrote: >> I don't feel good about this check, but it is done elsewhere in the same >> file ("prog == 0"). >> --- >> tests/shaders/shader_runner.c | 8 ++-- >>

[Piglit] [PATCH] shader_runner: fix GL_SHADER_STORAGE_BLOCK enum name

2015-11-24 Thread Samuel Iglesias Gonsálvez
Signed-off-by: Samuel Iglesias Gonsálvez --- tests/shaders/shader_runner.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/shaders/shader_runner.c b/tests/shaders/shader_runner.c index 9308905..14bca06 100644 --- a/tests/shaders/shader_runner.c +++

Re: [Piglit] [PATCH][RFC] Add dmesg option for reboot policy

2015-11-24 Thread Martin Peres
On 24/11/15 07:09, Dylan Baker wrote: On Mon, Nov 23, 2015 at 08:54:46PM -0500, Ilia Mirkin wrote: On Mon, Nov 23, 2015 at 8:41 PM, Dylan Baker wrote: On Mon, Nov 23, 2015 at 08:24:22PM -0500, Ilia Mirkin wrote: On Mon, Nov 23, 2015 at 8:07 PM, Dylan Baker

[Piglit] [PATCH v2] sso: test program pipeline with atomic counters

2015-11-24 Thread Tapani Pälli
Test fails on current Mesa and NVIDIA binary driver version 355.11, don't have currently AMD machine to test with. v2: - add error checks - modify to render points - make it possible to use regular program (makes test pass on Mesa) Signed-off-by: Tapani Pälli ---

Re: [Piglit] [PATCH] Add dmesg option for reboot policy

2015-11-24 Thread Emil Velikov
Hi Yan, The plan of having such a module is pretty sound. That said I think that the actual policy/implementation could use some tweaks. On 24 November 2015 at 12:14, wrote: > From: Yann Argotti > Date: Tue, 24 Nov 2015 12:16:34

Re: [Piglit] [PATCH][RFC] Add dmesg option for reboot policy

2015-11-24 Thread Ilia Mirkin
On Tue, Nov 24, 2015 at 5:33 AM, Martin Peres wrote: > On 24/11/15 07:09, Dylan Baker wrote: >> >> On Mon, Nov 23, 2015 at 08:54:46PM -0500, Ilia Mirkin wrote: >>> >>> On Mon, Nov 23, 2015 at 8:41 PM, Dylan Baker >>> wrote: On Mon,

[Piglit] [PATCH] Add dmesg option for reboot policy

2015-11-24 Thread yann . argotti
From: Yann Argotti Date: Tue, 24 Nov 2015 12:16:34 +0100 This adds a policy which advises when user should reboot system to avoid noisy test results due to system becoming unstable, for instance, and therefore continues testing successfully. To do this, a new