Re: [Piglit] [PATCH 1/2] unittests: Add test for DriverClassifier.get_glxinfo

piglit is broken on python3 without these, I'm planning to push soon. Quoting Dylan Baker (2016-09-16 13:46:04) > Ensure that it converts bytes to str and also collects correctly. > > Signed-off-by: Dylan Baker > --- > unittests/framework/test_driver_classifier.py |

[Piglit] Using piglit to nudge proprietary driver vendors

I know AMD has responded nicely to reports from people running piglit ( https://community.amd.com/thread/159406 ), and Nvidia actually mentioned piglit in one release note ( http://us.download.nvidia.com/Windows/347.52/347.52-win8-win7-winvista-desktop-release-notes.pdf ), so I guess it's doing

[Piglit] [PATCH 2/2] framework: Make driver_classifier convert to str (unicode)

In python2 the code as is works, although there might be odd corners. In python 3 it fails because the code tries to match bytes and strs, which doesn't work at all. This patch fixes the issue by converting the output from bytes to str (unicode) immediately, so we don't have to think about it

[Piglit] [PATCH 1/2] unittests: Add test for DriverClassifier.get_glxinfo

Ensure that it converts bytes to str and also collects correctly. Signed-off-by: Dylan Baker --- unittests/framework/test_driver_classifier.py | 25 + 1 file changed, 25 insertions(+) diff --git a/unittests/framework/test_driver_classifier.py

[Piglit] [PATCH] arb_viewport_array: rework tests to work with GL_OES_viewport_array

This makes some fairly simple changes to the existing tests to also work with GL_OES_viewport_array, which presents largely identical functionality. All of the tests continue to pass with desktop GL, and also work with my soon-to-be-posted GL ES implementation for mesa. Signed-off-by: Ilia Mirkin

Re: [Piglit] Fresh driver_classifier.py type error fix

Yeah, really I just wanted to report the bug. ___ Piglit mailing list Piglit@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/piglit

Re: [Piglit] Fresh driver_classifier.py type error fix

Quoting Dan Kegel (2016-09-16 09:12:21) > piglit stopped working for me this morning with a TypeError on ubuntu 16.04. > That's what I get for running off of tip, the file that broke was only > created six hours ago :-) > > Here's a tiny change that got me running again. > > From

[Piglit] Fresh driver_classifier.py type error fix

piglit stopped working for me this morning with a TypeError on ubuntu 16.04. That's what I get for running off of tip, the file that broke was only created six hours ago :-) Here's a tiny change that got me running again. From 80a2d9c6d7eaa322e87a4400d9bb2076d0341b35 Mon Sep 17 00:00:00 2001

Re: [Piglit] [PATCH 0/3] apitrace test runner for piglit

On 16/09/16 11:05, Eric Anholt wrote: Jose Fonseca writes: On 14/09/16 11:03, Eric Anholt wrote: I've applied Dylan's comments to the RFC series, and I've pushed a starting trace-db with reference images for my i965 and vc4: https://github.com/anholt/trace-db Eric,

Re: [Piglit] [PATCH] arb_query_buffer_object: beef up the test

On 16.09.2016 10:44, Alejandro Piñeiro wrote: On 15/09/16 18:02, Nicolai Hähnle wrote: From: Nicolai Hähnle A bunch of additions to the ARB_query_buffer_object test: 1. test different result types (including 64 bit types) 2. compare the written result with equality

Re: [Piglit] [PATCH 0/3] apitrace test runner for piglit

Jose Fonseca writes: > On 14/09/16 11:03, Eric Anholt wrote: >> I've applied Dylan's comments to the RFC series, and I've pushed a >> starting trace-db with reference images for my i965 and vc4: >> >> https://github.com/anholt/trace-db > > Eric, > > This is great initiative

Re: [Piglit] [PATCH 0/3] apitrace test runner for piglit

On 14/09/16 11:03, Eric Anholt wrote: I've applied Dylan's comments to the RFC series, and I've pushed a starting trace-db with reference images for my i965 and vc4: https://github.com/anholt/trace-db Eric, This is great initiative IMO. One suggestion: you can get much smaller traces by

Re: [Piglit] [PATCH] arb_query_buffer_object: beef up the test

On 15/09/16 18:02, Nicolai Hähnle wrote: > From: Nicolai Hähnle > > A bunch of additions to the ARB_query_buffer_object test: > > 1. test different result types (including 64 bit types) > 2. compare the written result with equality to the result obtained by >