October 2007 - Wine-Devel - list.winehq.org

Re: bug 9986

by Damjan Jovanovic

On 10/26/07, Reece Dunn <msclrhd(a)googlemail.com> wrote: > On 25/10/2007, Juan Lang <juan.lang(a)gmail.com> wrote: > > > Tests would also be useful here as well, so that there is not a regression. > > > > That's good general advice, but hard to implement without a serial > > device to test against, which our test systems won't have. > > You could always skip the tests when a serial connection is not > present. That way, you get coverage on systems that do have them. It > should be possible to configure Virtual Machines that have serial > ports suitable for use in these tests. > > If there are other factors that make this complicated to test (such as > getting repeatable results from the serial devices on machines that > have serial ports configured) then it is not worth the effort to > create tests for this case. > > Are there any existing tests for the serial port code? If there are, > that would suggest that this is possible. If we have serial port tests, then there aren't nearly enough. Check on bugzilla, virtually every serial port patch introduces at least 1 new regression, and these regressions generally don't get fixed, resulting in constantly deteriorating serial port support. Testing serial port hardware is very difficult because you need the tests to work on Windows, and you need everybody to have the hardware. You can emulate a serial port, but that requires kernel-mode drivers in at least Windows, and emulating hardware that plugs into the emulated port isn't much easier. Out of interest, Java and Mono both have serial port classes, do they do any serial port regression testing? > - Reece Damjan

Oct. 26, 2007

Re: Improving http://tests.winehq.org/data/

by Francois Gouget

On Fri, 26 Oct 2007, Robert Shearman wrote: [...] > Win9x's rpcrt4 is quite buggy and I don't think it's worth the trouble > of diagnosing what is happening and trying to work around it, both with > the crash and the test failures. Then rpcrt4_test should detect this and skip the server test. Otherwise it will show up as failed in the results and this will get reported again and again. -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ f u kn rd ts, ur wy 2 gky 4 ur wn gd.

Oct. 26, 2007

Re: bug 9986

by Francois Gouget

On Thu, 25 Oct 2007, Juan Lang wrote: > > Tests would also be useful here as well, so that there is not a regression. > > That's good general advice, but hard to implement without a serial > device to test against, which our test systems won't have. The tests could be set to only run in interactive mode. Then a Yess/No dialog could be displayed to the user to ask him if he has a connected serial device. -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ "Utilisateur" (nom commun) : Mot utilisé par les informaticiens en lieu et place d'"idiot".

Oct. 26, 2007

Re: d3dx8 math implementation + tests: use more "," instead of ";".

by Alexandre Julliard

Lionel Debroux <lionel_debroux(a)yahoo.fr> writes: > I noticed several "," in the implementation and tests of D3DX8 math > functions. I added more, since this may help the auto-vectorizer of > some compilers noticing that x86 SIMD could be used. I don't see any reason why that would make the slightest difference, what makes you think this is needed? -- Alexandre Julliard julliard(a)winehq.org

Oct. 26, 2007

Re: Improving http://tests.winehq.org/data/

by Robert Shearman

Huw Davies wrote: > On Fri, Oct 26, 2007 at 12:51:17AM +0200, Francois Gouget wrote: > >> So I had a closer look at the tests that failed to run: >> ... >> * rpcrt4:server crashes and then times out with the message box that >> says: >> This program has performed an illegal operation and will be >> shut down. >> >> RPCRT4_TEST caused an exception 6c6H in module RPCRT4.DLL at >> 015f:7fbd90c9. >> Registers: >> EAX=000006c6 CS=015f EIP=7fbd90c9 EFLGS=00010246 >> EBX=0075f978 SS=0167 ESP=0075f868 EBP=0075f9b8 >> ECX=00000000 DS=0167 ESI=0075f970 FS=300f >> EDX=00530f14 ES=0167 EDI=0075f890 GS=0000 >> Bytes at CS:EIP: >> e9 4a 46 00 00 55 8b ec 83 ec 08 53 56 57 55 fc >> Stack dump: >> 7fbde7f5 000006c6 0075f890 00530540 00000019 00411414 0075f890 00431698 >> 004223e4 00000006 0075f970 00431698 00000000 00000000 00431680 0000001a >> The above probably does not help much so that this will have to be >> taken to a debugger... >> >> > > Actually it does help. 0x6c6 (== 1734) is the key and we have: > #define RPC_S_INVALID_BOUND 1734 > Win9x's rpcrt4 is quite buggy and I don't think it's worth the trouble of diagnosing what is happening and trying to work around it, both with the crash and the test failures. -- Rob Shearman

Oct. 26, 2007

Re: Anything wrong with my patch from 16.10. about w32x86andwin40creation?

by Alexandre Julliard

Markus Gömmel <m.goemmel(a)compulab.de> writes: > Hm, so you suggest putting it into WINSPOOL_LoadSystemPrinters()? Cause this > looks like the only function who is definitely called during wine startup, > isn't it? You could do it in GetPrinterDriverDirectory. > So we should include creation of "spool" and "spool/drivers" into this as > well? Probably, yes. -- Alexandre Julliard julliard(a)winehq.org

Oct. 26, 2007

Re: Improving http://tests.winehq.org/data/

by Francois Gouget

On Thu, 25 Oct 2007, James Hawkins wrote: [...] > I don't think that's fair to long tests, say msi:install. I don't think we have any long-running tests right now (except the 'ftp' tests but that's probably a bug). All the tests that time out do so because they do stuff that pops up a MessageBox and thus blocks them indefinitely. msi:install is no exception. I can now confirm that when I run it on Windows 98 I get firt a MessageBox telling me that: Service 'TestService' (TestService) could not be installed. Verify that you have sufficient privileges to install system services. And then a MessageBox telling me that it crashed: This program has performed an illegal operation and will be shut down. MSI_TEST caused an invalid page fault in module <unknown> at 0000:00000009. Registers: EAX=00b2f7e0 CS=015f EIP=00000009 EFLGS=00010297 EBX=0046a9b3 SS=0167 ESP=00b2f778 EBP=00b2fd78 ECX=f8294700 DS=0167 ESI=0046a198 FS=0fcf EDX=005800a8 ES=0167 EDI=00000711 GS=0000 Bytes at CS:EIP: 00 1f 05 65 04 70 00 65 04 70 00 54 ff 00 f0 d4 Stack dump: 00000167 00436173 00b2f7e0 00000000 00000002 0046a9c8 00b2f7a8 00b2f7cc 01020102 01020102 01020102 01020102 ffffffff 0000000b 00000009 00000008 So I think it's premature to devise schemes for skipping long tests. If anything the duration of 'make test' is more likely to explode due to the accumulation of individual tests (already more than 300), rather than due to a single test taking a long time. -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ RFC 2549: ftp://ftp.isi.edu/in-notes/rfc2549.txt IP over Avian Carriers with Quality of Service

Oct. 26, 2007

Re: Improving http://tests.winehq.org/data/

by Huw Davies

On Fri, Oct 26, 2007 at 12:51:17AM +0200, Francois Gouget wrote: > So I had a closer look at the tests that failed to run: >... > * rpcrt4:server crashes and then times out with the message box that > says: > This program has performed an illegal operation and will be > shut down. > > RPCRT4_TEST caused an exception 6c6H in module RPCRT4.DLL at > 015f:7fbd90c9. > Registers: > EAX=000006c6 CS=015f EIP=7fbd90c9 EFLGS=00010246 > EBX=0075f978 SS=0167 ESP=0075f868 EBP=0075f9b8 > ECX=00000000 DS=0167 ESI=0075f970 FS=300f > EDX=00530f14 ES=0167 EDI=0075f890 GS=0000 > Bytes at CS:EIP: > e9 4a 46 00 00 55 8b ec 83 ec 08 53 56 57 55 fc > Stack dump: > 7fbde7f5 000006c6 0075f890 00530540 00000019 00411414 0075f890 00431698 > 004223e4 00000006 0075f970 00431698 00000000 00000000 00431680 0000001a > The above probably does not help much so that this will have to be > taken to a debugger... > Actually it does help. 0x6c6 (== 1734) is the key and we have: #define RPC_S_INVALID_BOUND 1734 Huw. -- Huw Davies huw(a)codeweavers.com

Oct. 26, 2007

Re: ddraw:d3d tests failing consistently

by Francois Gouget

On Fri, 26 Oct 2007, Reece Dunn wrote: [...] > This would mean that the tests that are consistently (and predictably) > failing under vmware will not show up on the test failures, so we can > investigate actual failures. Well, as far as I know, except for Direct3D and maybe sound issues, VMware systems behave like normal Windows boxes. In addition the tests I have run are on VMware 5.5 which does not have any of the 3D acceleration that they added in 6.0. So the relevant tests should be easy to skip, either by detecting lack of any 3D support or in the worst case by detecting the name of the graphics /sound card. -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ Research is the transformation of money to knowledge. Innovation is the transformation of knowledge to money. -- Dr. Hans Meixner

Oct. 26, 2007

Re: Word crash

by Kai Blin

On Friday 26 October 2007 09:28:09 Marco Stornelli wrote: > Hi all, > > I'm using wine 0.9.44-15 for openSuse 10.3 and office 2000. Excel > works fine, powerpnt doesn't start and wine doesn't print nothing in > console about it, and about word, wine prints this: Please don't send emails to wine-bugs. Open a bugreport on http://bugs.winehq.org/ instead. Cheers, Kai -- Kai Blin WorldForge developer http://www.worldforge.org/ Wine developer http://wiki.winehq.org/KaiBlin Samba team member http://www.samba.org/samba/team/ -- Will code for cotton.

Oct. 26, 2007