http://wiki.winehq.org/MakeTestFailures I downloaded and compiled from bleding-edge git and ran these last night. I boggled slightly when the unit testing actually crashed X (Kubuntu Hardy, kwin) - is anyone else getting this? I ran the tests again in failsafe (just a naked xterm - or, rather, konsole - and no window manager) and they finished and submitted OK. (Are others running these? By the way, are they very useful to the devs in these last couple of weeks before 1.0?) - d.
On Fri, May 30, 2008 at 1:51 PM, David Gerard <dgerard at gmail.com> wrote:> http://wiki.winehq.org/MakeTestFailures > > I downloaded and compiled from bleding-edge git and ran these last > night. I boggled slightly when the unit testing actually crashed X > (Kubuntu Hardy, kwin) - is anyone else getting this? I ran the tests > again in failsafe (just a naked xterm - or, rather, konsole - and no > window manager) and they finished and submitted OK.Kde3/4? When I ran kubuntu I'd frequently get crashes in plasma/kwin. If X is crashing, you need to check your graphics drivers.> (Are others running these? By the way, are they very useful to the > devs in these last couple of weeks before 1.0?)Yes, several people/developers run them daily. They are VERY useful, especially before 1.0, where a lot of effort has been made to squash those remaining bugs (James H especially has done a lot here). To see the test data: http://test.winehq.org/data/?C=M;O=D
David Gerard wrote:> > > Then I'm surprised how few tests I see there - all the Wine users in > the world who can work "./configure && make" but aren't coders should > be submitting test data, surely ... > - d.Well, if they're like me, they submitted tests after the first post asking for them, and didn't realize it should be done repeatedly. So maybe we need periodic reminders? I just submitted mine. I use KDE 3.5.9 too, and X did not crash for me. But I'm on openSUSE, and my onboard graphics is NVIDIA GeForce 6150LE.
2008/5/30 David Gerard <dgerard at gmail.com>:> http://wiki.winehq.org/MakeTestFailuresLooking at test.winehq.org, I appear to be the only person in the world bothering to do this! It's really not hard ... Quick guide: (Dan etc., please check over!) INITIAL SETUP: Get the code, build it the first time, run the tests the first time: cd # start from your home directory git clone git://source.winehq.org/git/wine.git wine # takes 30-60 min cd wine ./tools/wineinstall # takes 30-60 min cd programs/winetest sh dotests [your-unique-tag] # takes about 15 minutes for me You now have a full source tree and a compiled copy of Wine. SUBSEQUENT DAILY TESTS: cd ~/wine git fetch origin; git rebase origin # quite quick If there's been no changes in the past day, stop here. If there have been changes: make # build just the changes; takes 5-10 minutes for me cd programs/winetest sh dotests [your-unique-tag] The bit marked [your-unique-tag] should be some identifier for you and the system you're testing on, e.g. I use dgerard-hardy-6710b (me, my copy of Ubuntu, my laptop). - d.