Quoting Eric Anholt (2016-09-14 03:03:28)
> 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 Anholt (3):
> framework: Add a driver classifier based on the renderer
For the apitrace test runner, I need to be able to store known-good
images for various drivers, which means I need some way to group
drivers. Not all Mesa drivers we care about are covered here, but
this is a sample to get things started.
v2: Apply feedback from Dylan, add classification for my
v2: Apply feedback from Dylan
---
tests/apitrace/test-trace.py | 149 +++
1 file changed, 149 insertions(+)
create mode 100755 tests/apitrace/test-trace.py
diff --git a/tests/apitrace/test-trace.py b/tests/apitrace/test-trace.py
new file mode 100755
index
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 Anholt (3):
framework: Add a driver classifier based on the renderer string.
apitrace: Add a script for capturing and
---
framework/test/piglit_test.py | 1 +
tests/all.py | 22 +-
2 files changed, 22 insertions(+), 1 deletion(-)
diff --git a/framework/test/piglit_test.py b/framework/test/piglit_test.py
index 73bf65344264..571464bee48a 100644
---
Fixing some english language nitpicks below (and as a non-native english
speaker I could be wrong) and one typo:
Reviewed-by: Alejandro Piñeiro
On 14/09/16 02:01, Timothy Arceri wrote:
> These test so called complex loop unrolling in Mesa which just means
> unrolling a