GSoC Idea: Tools - Winetest Scripting Interface

[Stefan Dösinger]

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

Am 2016-02-28 um 13:32 schrieb Zhenbo Li:
> IMHO, this project should provide a convenient interface for both 
> piglit and human developers. Do you have any ideas that which
> function this script should provide?
The interesting thing is splitting up the output of the big d3d tests
in e.g. dlls/d3d9/tests/visual.c into reasonable chunks, preferably
matching the functions the tests are in. So that you go from
"d3d9/visual is failing" to "d3d9/visual/depth_bounds_test failed,
d3d9/visual/test_vshader_input successful".

Ideally this should be stable with regard to changes to the tests.
E.g. if 10 lines of code are added at the top of the file it shouldn't
break your output processing because the failing ok() lines are in
different lines of the file now.

The testbot is mostly able to do those things. I don't think it is
able to match line number to function name though.

Most of the tests in wine are not interesting to mesa. I expect them
to care about d3d and GL related stuff, maybe gdi, but something like
riched20 or wininet isn't really related to the GL library.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJW0yerAAoJEN0/YqbEcdMw1V0P/2oJhxOHOiHmzKfOOjD7Mz9B
EOrx40NdLzFsFOrMjTXp6iJCB/0WFxtUAqtK8KTM29sGT+FJoF+0roj59wIEfcm8
0x7esnhyOnFs6uj50DSHlByjF2BeqAxkfh/sYhgedS1XJJr2oW5UiHMiTRBW0ePb
jF/2frdOnnpQH2IY/ruf/PW/bwX+kzzCAuHWm3cxB2pYMjfk9NoNp+gDyGrnJyAK
u4zNXqvb/qMIcJjSwcnHlyr08rH6dcIYa7JcPNazzE5UGbHDX0z/Zl4XM2aayTOA
lhBLQEYZiVebpcdJLXjVLdgc7jFSxY+nKgpUK3WYZ5SOSMMN7p/6sVWt6/3AxUQU
BXs96luZ/g1myPJPSKGczfiWUz4Ij+1qd6SY+zlhjlkC0uNKqUb05zt1EPf5vVci
QWfbfikwqQdEimkYFduE6Mdfta/tL3lqibeLomdBSk/Mx9ku28pKEnLGYZfh8BAM
ZUtQJDfiAGTkaQEV8DCoAKqsIV6e1Ao49Ma8+o4upaktPj6NSUejy6Inkz9D5zWR
nqyrJvme+z63BHeOJxyL9+XGu4WjPwPsTbbfXuUNtWhW16mRi3R6dmBaVZm+ecgM
KXNctlVQdbgKkpQCE8e5qE4wKTpLjPL9aVmLzH3bxbVNIw6lRUJ0pqjATca82MZL
3HGnwp9DWSzEYoJvbp0r
=JQlp
-----END PGP SIGNATURE-----