From: José Fonseca jfons...@vmware.com
Handy until we have waffle everywhere.
---
.../piglit-framework-gl/piglit_glut_framework.c| 30 +++---
1 file changed, 27 insertions(+), 3 deletions(-)
diff --git a/tests/util/piglit-framework-gl/piglit_glut_framework.c
See tests/util/piglit-framework-gl/piglit_glut_framework.c:84:
default_reshape_func(int w, int h)
{
if (piglit_automatic
(w != piglit_width ||
h != piglit_height)) {
printf(Got spurious window resize in automatic run
(%d,%d
On 23 April 2014 19:29, Ilia Mirkin imir...@alum.mit.edu wrote:
On Wed, Apr 23, 2014 at 2:25 PM, Daniel Vetter dan...@ffwll.ch wrote:
On Wed, Apr 23, 2014 at 12:46:23PM -0400, Ilia Mirkin wrote:
So this means that going from Skip (or NotRun) to Timeout would not be
counted as a change
Both patches look OK to me.
Reviewed-by: Brian Paul bri...@vmware.com
On 04/24/2014 03:03 AM, jfons...@vmware.com wrote:
From: José Fonseca jfons...@vmware.com
Handy until we have waffle everywhere.
---
.../piglit-framework-gl/piglit_glut_framework.c| 30 +++---
1 file
Signed-off-by: Thomas Wood thomas.w...@intel.com
Cc: Daniel Vetter daniel.vet...@ffwll.ch
---
framework/log.py | 3 ++-
framework/status.py | 12
framework/summary.py | 6 --
framework/tests/status_tests.py | 3 ++-
The following revised patch reverts to using a normal Status class for the
timeout status and also adds a few tests to summary_tests.py, as suggested by
Ilia Mirkin.
Thomas Wood (1):
framework: add support for a timeout status
framework/log.py | 3 ++-
framework/status.py
On Apr 23, 2014 1:36 PM, Chad Versace chad.vers...@linux.intel.com
wrote:
On Tue, Apr 22, 2014 at 12:22:12PM -0700, Sarah Sharp wrote:
On Fri, Apr 18, 2014 at 06:21:31PM -0700, Jamey Sharp wrote:
- I don't see that MSC has to change at all even after two
eglSwapBuffers calls, if
Currently we call join after initializing both of the pools, which means
that they run simultaneously. This patch fixes that by creating a helper
function which sets off the pool, closes it, and then joins it. This
fixes the problem by forcing each pool to run in series.
v2: - Fix typo that put
On Thu, Apr 24, 2014 at 1:10 PM, Dylan Baker baker.dyla...@gmail.com wrote:
Currently we call join after initializing both of the pools, which means
that they run simultaneously. This patch fixes that by creating a helper
function which sets off the pool, closes it, and then joins it. This
On Thu, Apr 24, 2014 at 09:17:50AM -0700, Jamey Sharp wrote:
On Apr 23, 2014 1:36 PM, Chad Versace chad.vers...@linux.intel.com wrote:
On Tue, Apr 22, 2014 at 12:22:12PM -0700, Sarah Sharp wrote:
On Fri, Apr 18, 2014 at 06:21:31PM -0700, Jamey Sharp wrote:
- I don't see that MSC has to
Eric said:
But then there's the broken configure caching that makes it so you have
to git clean regularly, and the broken library directory handling. I
mean, look at the workarounds in chad's [Piglit] [ANNOUNCE] waffle =
1.3 required, you may need to rerun CMake. This build system is
The original one didn't test the GL_ONE and GL_ZERO terms and was
pretty compilicated. This tests all swizzle combinations and is
much simpler.
---
tests/all.py |1 +
tests/spec/ext_texture_swizzle/CMakeLists.gl.txt |1 +
Replaced by spec/ext_texture_swizzle/api.c and swizzle.c tests.
---
tests/all.py |1 -
tests/glean/CMakeLists.gl.txt |1 -
tests/glean/ttexswizzle.cpp | 435 -
tests/glean/ttexswizzle.h | 88 -
4 files changed, 525
Test for API errors and glGet for GL_EXT_texture_swizzle.
---
tests/all.py |1 +
tests/spec/ext_texture_swizzle/CMakeLists.gl.txt |1 +
tests/spec/ext_texture_swizzle/api.c | 122 ++
3 files changed, 124 insertions(+)
I'm not sure I undertand this. I think the limitation for
non-concurrent tests is that they cannot be concurrently, because they
do front buffer rendering and other things. That doesn't mean all the
off-screen tests cannot be run with the non-concurrent tests
simultaneously.
Marek
On Thu, Apr
On Friday, April 25, 2014 00:24:47 Marek Olšák wrote:
I'm not sure I undertand this. I think the limitation for
non-concurrent tests is that they cannot be concurrently, because they
do front buffer rendering and other things. That doesn't mean all the
off-screen tests cannot be run with the
On Thu, Apr 24, 2014 at 6:33 PM, Dylan Baker baker.dyla...@gmail.com wrote:
On Friday, April 25, 2014 00:24:47 Marek Olšák wrote:
I'm not sure I undertand this. I think the limitation for
non-concurrent tests is that they cannot be concurrently, because they
do front buffer rendering and
On Thursday, April 24, 2014 18:39:44 Ilia Mirkin wrote:
On Thu, Apr 24, 2014 at 6:33 PM, Dylan Baker
baker.dyla...@gmail.com wrote:
On Friday, April 25, 2014 00:24:47 Marek Olšák wrote:
I'm not sure I undertand this. I think the limitation for
non-concurrent tests is that they cannot be
There are 3 categories of tests:
- concurrent, these are off-screen and can be run anytime
- non-concurrent, because they render to a window (usually a front
buffer) and may take focus; any number of off-screen tests can be run
simultaneously with these, because off-screen tests cannot affect
Test the EGL_CHROMIUM_sync_control extension, which is similar to
the GLX_OML_sync_control extension:
http://www.opengl.org/registry/specs/OML/glx_sync_control.txt
The extension only defines one new function,
EGL_CHROMIUM_get_sync_values, which is equivalent to the
glXGetSyncValuesOML function.
For future EGL tests, I want to be able to use Chad's new piglit EGL
subtest infrastructure, and use the EGL utilities convenience functions
to set up a window, surface, and context.
Currently, egl_util_run calls piglit_report_result() after calling
test.draw. This means no other subtests get
With this patch tests with subtests are treated as groups, their status
is thrown away, and they inherit the 'worst' status from their children
just like a group.
This reverts commit de4b13de226e140313c3571e59a57438626da183.
---
framework/summary.py | 86
These tests are meant to show that subtest handling actually works.
---
framework/tests/summary_tests.py | 77 +++-
1 file changed, 76 insertions(+), 1 deletion(-)
diff --git a/framework/tests/summary_tests.py b/framework/tests/summary_tests.py
index
Since subtests are better handled in the summary module there is no need
to record these multiple times. This significantly reduces the size of
the results file, (from 45M to 10M)
---
framework/exectest.py | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git
24 matches
Mail list logo
