Most of these are pretty old at this point (over a year), and it seems
unlikely anyone still has results in those formats. The biggest problem
with them is that some of them (especially the early ones) are complex
transformations with a lot of validation needed, and some of the middle
ones rely on
Currently piglit's JSON format loading is tightly integrated with it's class
representations of result data. This has the advantage of reducing code
duplication, and making it easy to ensure that all data is correctly translated
to it's types. However, there is a drawback, the tight coupling makes
On Sun, 2016-10-09 at 11:10 +0200, Niels Ole Salscheider wrote:
> v5: Use sscanf, fix CL_DEVICE_OPENCL_C_VERSION include guard, fix logic
> v4: Test against env->version instead of opencl_version and never
> report PIGLIT_SKIP for the values of IMAGE_SUPPORT and ENDIAN_LITTLE
> v3: Fix
Reviewed-by: Tapani Pälli
On 10/04/2016 06:36 PM, Marek Olšák wrote:
From: Marek Olšák
---
.../execution/fs-texture-select.shader_test| 34 ++
1 file changed, 34 insertions(+)
create mode 100644