Call for winetest ing

Jeremy White jwhite at
Tue Feb 5 11:43:24 CST 2008

> If some people went through the trouble of using buildid's and not the
> precompiled winetest, along with documenting their hardware/OS on a
> wiki page, for instance, then we could more information on where
> specific failures are occuring. For instance, I noticed Joapa was
> reporting some MSI bugs, and was the only one posting an MSI failure
> in the make test usually failing bug.

Actually, I think there is a better solution.  If we want to capture
additional system information, and there is a command line tool that
would allow that, we can do so in the new 'runtests' script.

Right now, I have it capturing gcc, glibc, and kernel version info,
and that is all readily available as part of the nifty winetest results page.

We could also conceivably add info on processor count and ram size,
as well as video and audio card.  (But those would require slightly
more sophisticated scripts to postprocess; we don't want to just
dump the results of xdpyinfo for example...).



More information about the wine-devel mailing list