August 2011 - Wine-Devel - list.winehq.org

Re: buildbot status

by Dan Kegel

On Wed, Aug 31, 2011 at 3:53 PM, Stefan Dösinger <stefandoesinger(a)gmx.at> wrote: > On the other hand I think having a hardware with "strange" limits in the > testbot system can help to avoid getting bad assumptions about those limits > into the code, so I'll spend a day or two trying to isolate the issues and at > least file bug reports for Mesa and Wine, and actually running the buildbot to > see if this ancient machine can at least keep up with the d3d and d3dx > patches. it'd probably be a better use of time to bring up a modern ati system?

Aug. 31, 2011

Re: buildbot status

by Stefan Dösinger

On Sunday 28 August 2011 17:52:21 Dan Kegel wrote: > On Sun, Aug 28, 2011 at 2:16 AM, Stefan Dösinger <stefandoesinger(a)gmx.at> wrote: > > Is it possible to set up a slave that e.g. runs only the d3d tests? I > > have some older machines with older GPUs that are still worth > > covering(Radeon X1600, Geforce 7, maybe even the Radeon 9000 mobility), > > but I am not sure if the machines as a whole are powerful enough to run > > all the tests. I think there isn't really a need to run the mostly > > platform independent tests like msi and shell32 everywhere. > > Yes, I can set up a builder type that only triggers on d3d-related changes > and only runs d3d tests. I got the r200 machine updated to a point where I could run buildbot, but I realized that the days when this GPU/driver passed the tests are long gone. A few of those failures are low hanging fruits, at least as far writing bug reports is concerned, but others need more debugging. The kinds of failures(vertex shaders are completely broken, for example) make me doubt that we have more than a handful of users using this sort of hardware, otherwise we'd have more bug reports about them. On the other hand I think having a hardware with "strange" limits in the testbot system can help to avoid getting bad assumptions about those limits into the code, so I'll spend a day or two trying to isolate the issues and at least file bug reports for Mesa and Wine, and actually running the buildbot to see if this ancient machine can at least keep up with the d3d and d3dx patches.

Aug. 31, 2011

Re: fake patch #2 just to test error emails

by buildbot＠kegel.com

The Buildbot has detected a failed build on builder runtests while building Wine. Full details are available at: http://buildbot.kegel.com/builders/runtests/builds/166 BUILD FAILED: failed git For more info about this message, see http://wiki.winehq.org/BuildBot

Aug. 31, 2011

Re: cmd/tests: Add README doc file

by Alexandre Julliard

Octavian Voicu <octavian.voicu(a)gmail.com> writes: > 2011/8/31 Alexandre Julliard <julliard(a)winehq.org>: >> That sort of thing should be on the wiki. READMEs in the source are >> never maintained properly. > > Speaking of obsolete documentation, we should remove the > documentation/ChangeLog.* files. They haven't been updated since wine > 1.0 and are confusing. I tried sending a patch to remove them, but the > patch had 9 MB and I'm guessing it didn't go through. Only you can > remove them I guess, if you agree :) I don't. They are not supposed to be updated, but they are the historic record and should be preserved. -- Alexandre Julliard julliard(a)winehq.org

Aug. 31, 2011

Re: 78217: Subject: [PATCH 3/3] winecfg: Remove driver selection from Audio tab

by Dan Kegel

Ah, I see you resent a fixed version, sorry for the noise. (FWIW, the bot won't test your retry, since it was an incomplete patch series.) On Wed, Aug 31, 2011 at 1:22 PM, Dan Kegel <dank(a)kegel.com> wrote: > On Wed, Aug 31, 2011 at 1:10 PM, <buildbot(a)buildbot.kegel.com> wrote: >> The Buildbot has detected a failed build on builder runtests while building Wine. >> Full details are available at: http://buildbot.kegel.com/builders/runtests/builds/161 >> BUILD FAILED: failed git > > Something's fishy; looking at > http://marc.info/?l=wine-patches&m=131134541100364&w=2 > I see that the July 22nd version seems to have interesting strings, > but the August 31st version has all question marks when it comes to > non-ascii text. > What happened between the two? > > http://source.winehq.org/patches/data/78217, which is where I pulled > the patch from, > also has the question marks. >

Aug. 31, 2011

Re: 78217: Subject: [PATCH 3/3] winecfg: Remove driver selection from Audio tab

by Dan Kegel

On Wed, Aug 31, 2011 at 1:10 PM, <buildbot(a)buildbot.kegel.com> wrote: > The Buildbot has detected a failed build on builder runtests while building Wine. > Full details are available at: http://buildbot.kegel.com/builders/runtests/builds/161 > BUILD FAILED: failed git Something's fishy; looking at http://marc.info/?l=wine-patches&m=131134541100364&w=2 I see that the July 22nd version seems to have interesting strings, but the August 31st version has all question marks when it comes to non-ascii text. What happened between the two? http://source.winehq.org/patches/data/78217, which is where I pulled the patch from, also has the question marks.

Aug. 31, 2011

Re: 78214: Subject: winusb: add new stub dll (resend)

by Dan Kegel

On Wed, Aug 31, 2011 at 1:00 PM, <buildbot(a)buildbot.kegel.com> wrote: > The Buildbot has detected a failed build on builder runtests while building Wine. > Full details are available at: http://buildbot.kegel.com/builders/runtests/builds/158 > BUILD FAILED: failed git > > > For more info about this message, see http://wiki.winehq.org/BuildBot The error was fatal: corrupt patch at line 32 Your email program may have removed whitespace from the patch. Try attaching the patch instead of including it inline.

Aug. 31, 2011

Re: [PATCH 1/5] cmd/tests: add more tests for command line parsing

by Frédéric Delanoy

2011/8/31 Frédéric Delanoy <frederic.delanoy(a)gmail.com>: > 2011/8/31 Frédéric Delanoy <frederic.delanoy(a)gmail.com>: >> 2011/8/31 Martin Wilck <mwilck(a)arcor.de>: >>>> Just ask if you don't understand the @keywords(a). Doc is a bit lacking; >>>> I might add a quick wiki help page if desired. >>> >>> Yes, that'd be helpful (IMO just a README file in the tests/ directory >>> would be even better). It took me a while to get started with the cmd >>> testing code. > > Submitted in http://source.winehq.org/patches/data/78195 but Alexandre > prefers a wiki page so I'll convert it. Available on http://wiki.winehq.org/CmdConformanceTests

Aug. 31, 2011

Re: cmd/tests: Add README doc file

by Octavian Voicu

2011/8/31 Alexandre Julliard <julliard(a)winehq.org>: > That sort of thing should be on the wiki. READMEs in the source are > never maintained properly. Speaking of obsolete documentation, we should remove the documentation/ChangeLog.* files. They haven't been updated since wine 1.0 and are confusing. I tried sending a patch to remove them, but the patch had 9 MB and I'm guessing it didn't go through. Only you can remove them I guess, if you agree :) Octavian

Aug. 31, 2011

Re: d3dx9_36/tests: Fix printing a NULL string

by David Laight

On Wed, Aug 31, 2011 at 05:18:57PM +0200, Joerg-Cyril.Hoehle(a)t-systems.com wrote: > Bruno Haible was so kind to provide the following test run results: > > glibc SIGSEGV > MacOS X 10.5 (null) > FreeBSD 6.4 (null) > OpenBSD 4.9 (null) > AIX 7.1 empty > HP-UX 11.31 empty > IRIX 6.5 (null) > OSF/1 5.1 (null) > Solaris 10 SIGSEGV > Cygwin (null) > mingw (null) > > for printf("%s", NULL) Some of the systems will have address zero valid and just read from that address. Some will generate a non zero length string. IIRC some very old OS (think vax and pdp11) arranged for address zero to contain zero (possibly as part of the program header) so that 'if (x && *x)' could be shortened to 'if (*x)'. Allowing address zero be mapped (eg by mmap()) is a bad idea as a kernel 'call through NULL ptr' can be used to escalate privs. David -- David Laight: david(a)l8s.co.uk

Aug. 31, 2011