[Piglit] Ideas for Wine Test Suite and Mesa Workflow

Zhenbo Li litimetal at gmail.com
Sat Feb 27 14:38:01 UTC 2016

2016-02-26 8:04 GMT+08:00 Dylan Baker <baker.dylan.c at gmail.com>:
> That will probably work, the only thing to consider with that approach is
> that it is more expensive to start an external process than interpret in
> piglit's Python process. If there aren't a lot of tests that may not be a
> big deal, but if there are thousands of tests you will start to see
> overhead.

Hello Dylan,

Thank you for pointing it out. I think it is not so critical.
I ran such code (in path/to/wine/code)

$ rm -rf ~/.wine && make clean && make
$ cd dlls/msxml3/tests
$ time make test

And got

real    0m12.117s
user    0m0.705s
sys 0m0.345s

If I use a python wrapper[1], I got

$ rm -rf ~/.wine && make clean && make
$ cd dlls/msxml3/tests
$ time python3 runner.py

real    0m12.633s
user    0m0.702s
sys 0m0.368s

[1]: runner.py

#!/usr/bin/env python3

import os

ret = os.system("make test")

Have a nice day!
Zhenbo Li

More information about the Piglit mailing list