GSoC Idea: Tools - Winetest Scripting Interface

Stefan Dösinger stefandoesinger at gmail.com
Sun Feb 14 11:35:51 CST 2016


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Am 2016-02-14 um 01:39 schrieb Zhenbo Li:
> Thank you for reading my proposal. I wonder that Stefan Dösinger
> might want a more complicated solution (No change to current code,
> and write a full-functional script from scratch)
My personal requirement is mostly "Get the Mesa developers to run our
d3d and GL tests as part of their development workflow". This is more
a political than an engineering question. I think the best thing to do
is to get in contact with Mesa people.

One possible approach is to rewrite every Wine test as a Piglit test,
but I think that would miss the point. Doing so would be a massive
duplication of work, and we wouldn't be able to catch unexpected
regressions. (Though it would cover very specific corner cases in a
way that is very convenient for Mesa devs since they don't have to
bother about Wine specifics at all.)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWwLr3AAoJEN0/YqbEcdMwUpQP/0w/AC5P3ofBU7coKbN3PfJI
tAnp94IwRE8Dj/WHWjkRBRsgPli+dxXMkNarGuCdkQQCCpku0HIny9e9oliV/iXX
tTrUuUkJ81+UA3pbiYtGllaIKRor1Jyph8uNjX/DXwvzP0XIPgLcdAdSPP2h0IR2
xFx5fBOC35sUcVtJB1yfw78ZrXIDR3jxEXQG65vwxAtbi63zpjVgyQNTU8n2afFq
KX+2w/3qh7l3T880QYkx9aR7KRyHZcn5OwYSDe3wWZHCXf7ourTONNk8knidZfL7
Q9YzTS6HoGdNp/yre5Uk+SqOpLnTIUfOLSewD1PwrTl0ix4BHxyU3q9EWE9klqAb
F0C7+9fT7W1/ud+ZEGo9QKL+flk8vRGnMQ/NKAKpyD266sGXaHJT/8n3lukBSADM
JgHljdfJPi49/4righxGHTUajN0vIwEO95sBaMMHjm5urCm/5zte9t8j+GmrBREw
GdZszyF5We0vjlq6VjUyZqr2iU2499ELPs3CAOTxk8mHZ69tEv8G6xTfurhaEiIv
h9Ob3iegDchrQQCQZYwiDXZeKB4IJhiwql2V0TBJ7LZpMZFVdIlDan3qvr0cF/tp
QMQmMnfdSDEQLRNmj3aQKq5JaitVv6gcSuCBkiQhoZjtesA7c53CrUKOWrKQfnt0
AG3A7Oe+SzJB+SRNys6H
=rSy7
-----END PGP SIGNATURE-----



More information about the wine-devel mailing list