Re: [Piglit] [Patch v2 10/11] exectest.py: Merge Test and ExecTest into a single class

2014-03-27 Thread Dylan Baker
On Thursday, March 27, 2014 17:01:24 Dylan Baker wrote: > On Thursday, March 27, 2014 15:34:03 Dylan Baker wrote: > > Rather than have 2 base classes, let's just have one. > > > > v2: - remove test that no longer is valid > > > > Signed-off-by: Dylan Baker > > --- > > > > framework/exectest.py

[Piglit] [Patch v2 10/11] exectest.py: Merge Test and ExecTest into a single class

2014-03-27 Thread Dylan Baker
Rather than have 2 base classes, let's just have one. v2: - remove test that no longer is valid Signed-off-by: Dylan Baker --- framework/exectest.py| 26 +- framework/gleantest.py | 12 ++-- framework/gtest.py | 4 ++-- framew

[Piglit] [Patch v2 07/11] glsl_parser_test.py: Simplify GLSLParserTest

2014-03-27 Thread Dylan Baker
This vastly simplifies the way that GLSLParserTest works. This simplification has a couple of advantages. First, we call PlainExecTest's __init__ rather than ExecTest's __init__, which is good OO practice; second we reduce the number of regex's used, which yields enhanced performance. In tests this

[Piglit] [Patch v2 03/11] framework/shader_test.py: Remove standalone capability

2014-03-27 Thread Dylan Baker
Shader_test has a bizarre capability to be run as a standalone script as well as be used as a module. This was probably useful when developing the original shader_test implementation, but at this point it's unused code just waiting to bit-rot adding needless complexity Signed-off-by: Dylan Baker

[Piglit] [Patch v2 11/11] python: Rename PlainExecTest to PiglitTest

2014-03-27 Thread Dylan Baker
Since PlainExecTest is either used directly or as a parent for running "native" piglit tests, it seems fitting to give it a name that reflects that purpose. This patch was mostly generated with the following command: find . -name '*.py' | xargs sed -i -e 's!PlainExecTest!PiglitTest!g Then a handf

[Piglit] [Patch v2 01/11] Replace end_config with 'end config' in glsl parser tests

2014-03-27 Thread Dylan Baker
The example glsl parser test doesn't list end_config as acceptable, and there are only 5 tests using end_config, so it makes sense to just fix those tests rather than generating slower more complicated regex for handling end_config. Signed-off-by: Dylan Baker --- .../spec/glsl-1.20/compiler/qual

[Piglit] [Patch v2 02/11] shader_tests_tests.py: Adds some tests for the shader_test module

2014-03-27 Thread Dylan Baker
This adds some additional tests for ShaderTest behavior. Some of these tests fail because of dumb implementation details. Signed-off-by: Dylan Baker --- framework/tests/shader_test_tests.py | 57 ++-- 1 file changed, 54 insertions(+), 3 deletions(-) diff --git a/

[Piglit] [Patch v2 05/11] Adds some tests for glsl_parser_tests.py

2014-03-27 Thread Dylan Baker
These tests model future behavior rather than current behavior, some of them pass, others fail. Signed-off-by: Dylan Baker --- framework/tests/glsl_parser_test_tests.py | 120 ++ framework/tests/glsl_parser_tests.py | 29 2 files changed, 120 insertions

[Piglit] [Patch v2 08/11] framework: Move Test from core to exectest

2014-03-27 Thread Dylan Baker
Since Test is exclusively used as a parent for ExecTest, the two classes should be in the same module. Signed-off-by: Dylan Baker --- framework/core.py| 70 -- framework/exectest.py| 72 +++- fram

[Piglit] [Patch v2 04/11] framework/shader_test.py: simplify ShaderTest

2014-03-27 Thread Dylan Baker
This patch almost completely reworks ShaderTest. It was originally much more complicated than was necessary, this code should be much easier to work with, and removes some quirks. One of those was that ShaderTest inherited from PlainExecTest, but used ExecTest's __init__ method, which has implicati

[Piglit] [Patch v2 09/11] framework: move testBinDir to exectest

2014-03-27 Thread Dylan Baker
This is mostly consumed by Test's children, so putting it in the same module makes sense. This should reduce the number of imports from core as well, since most consumers of testBinDir also make use of ExecTest or PlainExecTest. Signed-off-by: Dylan Baker --- framework/core.py

[Piglit] [Patch v2 06/11] glsl_parser_test.py: Remove standalone functionality.

2014-03-27 Thread Dylan Baker
This removes the standalone run functionality from glsl_parser_test. Like shader_test this was probably useful for testing while in development, but at this point it's just dead code. Signed-off-by: Dylan Baker --- framework/glsl_parser_test.py | 35 +-- 1 file ch

[Piglit] Refactor Test Classes v2

2014-03-27 Thread Dylan Baker
This series refactors and simplifies the Test classes in piglit. It's goal is to have a single abstract base class Test, which should be the parent of most test classes. PlainExecTest (renamed PiglitTest) derives from this class, while GLSLParserTest and ShaderTest derive from PiglitTest. IGTTest,

Re: [Piglit] [PATCH v2 3/3] Remove extra newline from the end of run message

2014-03-27 Thread Dylan Baker
On Thursday, March 27, 2014 15:52:49 Thomas Wood wrote: > The extra newline is no longer necessary as the final summary line > includes one. > > Signed-off-by: Thomas Wood > --- > piglit-resume.py | 3 +-- > piglit-run.py| 3 +-- > 2 files changed, 2 insertions(+), 4 deletions(-) > > diff --g

Re: [Piglit] [PATCH 12/13] cmake: Check for pthreads

2014-03-27 Thread Chad Versace
On Thu, Mar 27, 2014 at 08:08:50AM -0700, Jose Fonseca wrote: > I think it would be more portable to use FindThreads module that comes with > cmake. e.g.: > > find_package (Threads) > > target_link_libraries (my_program > ${CMAKE_THREAD_LIBS_INIT} > ) > > if (CMAKE_USE_PTHREADS_INIT

[Piglit] [PATCH v2 0/3] log output and final summary line

2014-03-27 Thread Thomas Wood
Updated series based on Dylan Baker's review. Thomas Wood (3): framework/log.py: ensure any previous output is cleared framework: print a summary line after a run has finished Remove extra newline from the end of run message framework/core.py | 2 ++ framework/log.py | 37 +++

[Piglit] [PATCH v2 2/3] framework: print a summary line after a run has finished

2014-03-27 Thread Thomas Wood
v2: split output writing into a private method (Dylan Baker) Signed-off-by: Thomas Wood --- framework/core.py | 2 ++ framework/log.py | 44 +++- 2 files changed, 29 insertions(+), 17 deletions(-) diff --git a/framework/core.py b/framework/core.py index

[Piglit] [PATCH v2 3/3] Remove extra newline from the end of run message

2014-03-27 Thread Thomas Wood
The extra newline is no longer necessary as the final summary line includes one. Signed-off-by: Thomas Wood --- piglit-resume.py | 3 +-- piglit-run.py| 3 +-- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/piglit-resume.py b/piglit-resume.py index c9cb72b..09d0664 100755 ---

[Piglit] [PATCH v2 1/3] framework/log.py: ensure any previous output is cleared

2014-03-27 Thread Thomas Wood
If the new summary line is shorter than the previous one, clear the remaining characters. v2: remove unused variable and use str.format (Dylan Baker) Signed-off-by: Thomas Wood --- framework/log.py | 19 ++- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/framewor

Re: [Piglit] [PATCH 12/13] cmake: Check for pthreads

2014-03-27 Thread Jose Fonseca
I think it would be more portable to use FindThreads module that comes with cmake. e.g.: find_package (Threads) target_link_libraries (my_program ${CMAKE_THREAD_LIBS_INIT} ) if (CMAKE_USE_PTHREADS_INIT) add_definitions(-DPIGLIT_HAS_PTHREADS) endif () etc. Jose - Origin

[Piglit] [PATCH] dlist-multidrawarrays: test that glMultiDrawArrays works in a display list

2014-03-27 Thread Brian Paul
v2: Also test GL_COMPILE_AND_EXECUTE mode. --- tests/all.py |1 + tests/spec/CMakeLists.txt |1 + tests/spec/gl-1.4/CMakeLists.gl.txt | 14 ++ tests/spec/gl-1.4/CMakeLists.txt |1 + tests/spec/gl-1.4/dlist-multidrawarrays.c