November 2009 - Wine-Devel - list.winehq.org

Re: Link to Test Runs

by Nate Gallaher

Tests can be found at test.winehq.org Mike wrote: > Ok, I found this once before but I can't find it again. Where is the link to the test runs for different platforms, etc. I wanted to see if my tests passed Win 95. > > Sorry for asking questions that should probably be obvious, but we all start ignorant and some of us more ignorant and naive than others. > > Thanks, > Mikey > > > > > >

Nov. 6, 2009

Link to Test Runs

by Mike

Ok, I found this once before but I can't find it again. Where is the link to the test runs for different platforms, etc. I wanted to see if my tests passed Win 95. Sorry for asking questions that should probably be obvious, but we all start ignorant and some of us more ignorant and naive than others. Thanks, Mikey

Nov. 6, 2009

Re: shell32/tests: Add Program Manager DDE Conformance Tests (try 2)

by Mike

Didn't copy first response to the devel list. Took an initial look and I think I know what is going on. I will try and get a patch finished by the end of the weekend to correct these. --- On Fri, 11/6/09, Paul Vriens <paul.vriens.wine(a)gmail.com> wrote: > From: Paul Vriens <paul.vriens.wine(a)gmail.com> > Subject: Re: shell32/tests: Add Program Manager DDE Conformance Tests (try 2) > To: "Mikey Alexander" <firesword14(a)yahoo.com> > Cc: wine-devel(a)winehq.org > Date: Friday, November 6, 2009, 12:43 AM > On 11/03/2009 04:32 AM, Mike wrote: > > These conformance tests are for the program manager > dde. Basic operations are tested. The current > wine implementation (shell32/dde.c) of the Program Manager > DDE is stubbed. This conformance tests were run and > passed on Win 98 SE and Win XP SP2. Related Bug #9159 > > > > > > --- > > dlls/shell32/tests/Makefile.in | > 1 + > > dlls/shell32/tests/progman_dde.c > | 551 ++++++++++++++++++++++++++++++++++++++ > > 2 files changed, 552 insertions(+), 0 > deletions(-) > > create mode 100644 > dlls/shell32/tests/progman_dde.c > > > > > > Hi Mikey, > > These new tests introduce test failures on different > platforms: > > http://test.winehq.org/data/tests/shell32:progman_dde.html > > Could you have a look? > > -- > Cheers, > > Paul. >

Nov. 6, 2009

To error out or to skip tests?

by Joerg-Cyril.Hoehle＠t-systems.com

Hi, I apologize for the numerous occurrances of red color on test.winehq due to my new winmm MCI tests. That was not expected. However, turning something green is not a goal in itself. For some time now I wanted to query wine-devel about this topic, independently of my patches, so here it goes. An analysis reveals that my tests implement a detector of vmware (virtualbox etc.) default installs, i.e. MS-Windows systems that have not been configured with sound. No real user's machines would be like that (except for a w95 box I tried with a broken soundcard). The revealing line is > Tests skipped: Please install audio driver. Tests will fail (18 errors) This goes hand in hand with "5 tests, 0 errors, 1 skip" in winmm:wave. Exactly those systems skipping the wave tests produce 18-19 MCI errors. Failure to flag an error in such cases has known drawbacks: - For several month, Austin did not notice that his BSD boxes had lost sound. wave.ok simply reports "5 tests ok, 1 skipped" in joyfull green, whereas it executed many tests half a year ago. - All those vmware boxes configured without sound and thus skipping all but 5 wave.ok tests have for monthes *not* provided valuable feedback to Wine. So they were actually *not* executing tests, when they could have. It's only when Paul tested one of my tests that he realized that sound was not configured on one of his vmware boxes, promptly configured the sound device, and the tests passed. The picture on test.winehq.org is a disaster: None of the w95, w98, nt4, 2k, 2k3, Vista, 2k8, w7 machines have performed winmm:wave tests! They all have no sound configured. Mostly useless. Therefore, I believe it's sometimes better to flag an error than to calmly skip something. Last year already, submitting the ICCVID patches, I was thinking: "iccvid.dll may not part of every installation, but we want feedback so we should compare behaviour with MS-Windows systems equipped with that library and ask people to install it if not present". Likewise, Wine should compare with systems similarly equipped: d3d8, d3d9, dplay, dmusic etc. Perhaps an easy change on test.winehq would be to augment the blue color indicator of skipped tests to the full rectangle surface instead of the current green? Of course, I'll change my tests to flag a single error on systems without sound. -- Or no error at all, if that's wine-devel consensus. What do you think? Jörg Höhle. There's only few real MCI test errors I saw on test.winehq: the system "fg_winxp-ie8" that yields 1 error instead of 18: mci.c:391: Test failed: not enough time elapsed 80ms -- a flakey test. And on the ME systems: mci.c:603: Test failed: mci re-auto-open status mode returned error: 275 mci.c:612: Test failed: mci auto-open pause returned error: 275 Luckily, there are a few machines that pass all tests.

Nov. 6, 2009

Re: winmm/tests: Add MCI waveaudio tests.

by Paul Vriens

On 11/05/2009 02:35 PM, Joerg-Cyril.Hoehle(a)t-systems.com wrote: > Hi, > > this is the same as yesterday's patch except that I replaced the > ad-hoc skip auto-open test with one that specifically detects Wine's > missing auto-open functionality instead of another thing missing in Wine. > You will prefer that version; sorry for the quick-shot. > > Regards, > Jörg Höhle. > Hi Jörg, This one introduces several test failures: http://test.winehq.org/data/tests/winmm:mci.html I guess you already noticed, but could you have a look? -- Cheers, Paul.

Nov. 6, 2009

Re: shell32/tests: Add Program Manager DDE Conformance Tests (try 2)

by Paul Vriens

On 11/03/2009 04:32 AM, Mike wrote: > These conformance tests are for the program manager dde. Basic operations are tested. The current wine implementation (shell32/dde.c) of the Program Manager DDE is stubbed. This conformance tests were run and passed on Win 98 SE and Win XP SP2. Related Bug #9159 > > > --- > dlls/shell32/tests/Makefile.in | 1 + > dlls/shell32/tests/progman_dde.c | 551 ++++++++++++++++++++++++++++++++++++++ > 2 files changed, 552 insertions(+), 0 deletions(-) > create mode 100644 dlls/shell32/tests/progman_dde.c > > Hi Mikey, These new tests introduce test failures on different platforms: http://test.winehq.org/data/tests/shell32:progman_dde.html Could you have a look? -- Cheers, Paul.

Nov. 6, 2009

Re: had trouble compiling today

by Susan Cragin

>Looks like a gcc compiler bug, so you will need to report it there >and/or to the Ubuntu bug tracker. > >Out of interest: > a/ did this work when you were running karmic? Yes. Worked always with Karmic. Worked yesterday with Lucid. But downloaded new gcc today, and new git. So it's one or the other. > b/ what does "gcc --version" produce? gcc (Ubuntu 4.4.2-1ubuntu3) 4.4.2 > c/ is this an incremental build from a previous build on karmic? Yes. (In fact, it's pre-alpha lucid.) It may well be that there is a new gcc that depends on a new something else that hasn't been released yet. > d/ what happens if you clean out all build files (running "git >clean -fxd" in ~/wine will do this if ~/wine is a clone of the wine >git repository) and do a build -- does that resolve the issue? Oh, that's a nice command. I'll have to remember that one. Nothing happens. >NOTE: You should still report this to gcc/Ubuntu. Noted. Reported. Bug filed. >- Reece As I was getting ready to send this I noted another gcc floating by aptitude, so I gave that one a spin. No luck. The problem persists, but I bet the developers know about it.

Nov. 6, 2009

Re: Wine on OpenBSD, Theo de Raadt

by David Laight

On Thu, Nov 05, 2009 at 02:21:47PM +0100, Yann Droneaud wrote: > And OpenBSD won't allow page 0 mapping for security reasons (and > performance reasons). > > Since Wine seems to be working on other *BSD and derivative systems, > is this a problem ? NetBSD is likely to disable user space mapping of address 0 some time in the near future - it does have problems with the compatibility code for other unix system binariess though (I can't remember which ones, compat-ultrix might be the one). David -- David Laight: david(a)l8s.co.uk

Nov. 5, 2009

Re: had trouble compiling today

by Reece Dunn

2009/11/5 Susan Cragin <susancragin(a)earthlink.net>: > It may be me. I've upgraded to Lucid Lynx. > My compile failed. > > gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wstrict-prototypes -Wwrite-strings -Wtype-limits -Wpointer-arith -g -O2 -o int21.o int21.c > int21.c: In function ‘INT21_GetDriveAllocInfo’: > int21.c:3556: internal compiler error: in int_cst_value, at tree.c:8305 > Please submit a full bug report, > with preprocessed source if appropriate. > See <file:///usr/share/doc/gcc-4.4/README.Bugs> for instructions. Looks like a gcc compiler bug, so you will need to report it there and/or to the Ubuntu bug tracker. Out of interest: a/ did this work when you were running karmic? b/ what does "gcc --version" produce? c/ is this an incremental build from a previous build on karmic? d/ what happens if you clean out all build files (running "git clean -fxd" in ~/wine will do this if ~/wine is a clone of the wine git repository) and do a build -- does that resolve the issue? NOTE: You should still report this to gcc/Ubuntu. - Reece

Nov. 5, 2009

had trouble compiling today

by Susan Cragin

It may be me. I've upgraded to Lucid Lynx. My compile failed. gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wstrict-prototypes -Wwrite-strings -Wtype-limits -Wpointer-arith -g -O2 -o int21.o int21.c int21.c: In function ‘INT21_GetDriveAllocInfo’: int21.c:3556: internal compiler error: in int_cst_value, at tree.c:8305 Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-4.4/README.Bugs> for instructions. make[2]: *** [int21.o] Error 1 make[2]: Leaving directory `/home/susan/wine/dlls/winedos' make[1]: *** [winedos] Error 2 make[1]: Leaving directory `/home/susan/wine/dlls' make: *** [dlls] Error 2 susan(a)ubuntu:~/wine$

Nov. 5, 2009