winetest experience
Reece Dunn
msclrhd at googlemail.com
Tue Feb 5 01:46:26 CST 2008
On 05/02/2008, Jeremy White <jwhite at codeweavers.com> wrote:
> Okay, so I boldly tried to use winetest with what documentation
> I could find, and had an...um...interesting time.
The easiest thing I found for generating test results on Wine is to
treat it like Windows. That is, download the
winetest-[buildid]-paul-mingw.exe from the build you want to test and
run:
wine winetest-[buildid]-paul-mingw.exe
e.g. on the http://test.winehq.org/data/200801301937/ page, the "Main
summary for build 200801301937", and downloaded
http://www.astro.gla.ac.uk/users/paulm/WRT/CrossBuilt/winetest-200801301937-paul-mingw.exe.
Then, I ran
./wine winetest-200801301937-paul-mingw.exe
from a build of wine-0.9.54 and followed the instructions on the
program. It did generate an error about not being able to clean the
log at the end, but it generated the "XP wine-0.9.54-notheme" and "XP
wine-0.9.54" results without any issues.
> So...what's the convention for build.id etc? And
> why didn't they get set?
Looking at the results from the Wine Test Shell, it is using a build timestamp.
- Reece
More information about the wine-devel
mailing list