Conformance tests fail with 20031016 build
Hi, The conformance tests fail for the 20031016 build on my system with the following error message: ../../../tools/runtest -q -P wine -M user32.dll -T ../../.. -p user32_test.exe.so msg.c && touch msg.ok msg.c:333: Test failed: ShowWindow:overlapped: in msg 0x0047 expecting wParam 0x47 got 0x0 I haven't gotten this error until recently. My system is fairly ancient, it's a debian woody installation with the latest version of KDE.
Hi, got the same errors here with Wine today CVS, updated RedHat & Gnome system. --- Sami Aario <sami.aario(a)surfeu.fi> a écrit :
Hi,
The conformance tests fail for the 20031016 build on my system with the following error message:
../../../tools/runtest -q -P wine -M user32.dll -T ../../.. -p user32_test.exe.so msg.c && touch msg.ok
msg.c:333: Test failed: ShowWindow:overlapped: in msg 0x0047 expecting wParam 0x47 got 0x0
I haven't gotten this error until recently. My system is fairly ancient, it's a debian woody installation
with the latest version of KDE.
===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 Say NO to software patents Dites NON aux brevets logiciels "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
Hi Sylvain, Sami, What settings are you using for wine? I don't see this problem with WRT, but I've only recently got it back up and running again. On a seperate note, some other strange things I've noticed: One of Monday night's patches seems to have broken a conformance test in listbox.c (line 123) but only for wine in win3.1-mode! Win3.1-mode also passes two todo tests (lines 129 and 134 both in the user/listbox.c). See http://www.astro.gla.ac.uk/users/paulm/WRT/buildinfo.php?id=400#tests-win31 Also, does anyone else get orphaned zombie processes after running the regression tests? (which is moderately impressive: I thought init was supposed to clean these up) I get about six zombies per regression test. I tracked one of these zombies down to the kernel/test/process.c test_DebuggingFlag()'s ContinueDebugEvent() call, which disappears into wineserver. If it helps, the list of installed RPMs is here: http://www.astro.gla.ac.uk/users/paulm/WRT/RPMs Any ideas? Ta, Paul. On Tue, 28 Oct 2003, [iso-8859-1] Sylvain Petreolle wrote:
Hi, got the same errors here with Wine today CVS, updated RedHat & Gnome system.
--- Sami Aario <sami.aario(a)surfeu.fi> a �crit :
The conformance tests fail for the 20031016 build on my system with the following error message: [...] msg.c:333: Test failed: ShowWindow:overlapped: in msg 0x0047 expecting wParam 0x47 got 0x0
---- Paul Millar
Hi Paul,
What settings are you using for wine? I don't see this problem with WRT, but I've only recently got it back up and running again.
What are the settings you want to know ?
On a seperate note, some other strange things I've noticed:
One of Monday night's patches seems to have broken a conformance test in listbox.c (line 123) but only for wine in win3.1-mode! Win3.1-mode also passes two todo tests (lines 129 and 134 both in the user/listbox.c). Got same results here. Every emulated OS passes except win31.
Also, does anyone else get orphaned zombie processes after running the regression tests? (which is moderately impressive: I thought init was supposed to clean these up)
I get some zombies too, and the kernel notices it. This is what I have in /var/log/messages: Oct 30 10:44:18 wine kernel: application bug: wine(2120) has SIGCHLD set to SIG_IGN but calls wait(). Oct 30 10:44:18 wine kernel: (see the NOTES section of 'man 2 wait'). Workaround activated. Talking about the kernel process test, it seems they are runned more than once, is it the normal way ? ../../../tools/runtest -q -P wine -M kernel32.dll -T ../../.. -p kernel32_test.exe.so process.c && touch process.ok tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures.
I get about six zombies per regression test. I tracked one of these zombies down to the kernel/test/process.c test_DebuggingFlag()'s ContinueDebugEvent() call, which disappears into wineserver.
===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 Say NO to software patents Dites NON aux brevets logiciels "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
Hi Sylvain, On Thu, 30 Oct 2003, [iso-8859-1] Sylvain Petreolle wrote:
What settings are you using for wine? I don't see this problem with WRT, but I've only recently got it back up and running again. What are the settings you want to know ?
~/.wine/config would be good.
On a seperate note, some other strange things I've noticed:
One of Monday night's patches seems to have broken a conformance test in listbox.c (line 123) but only for wine in win3.1-mode! Win3.1-mode also passes two todo tests (lines 129 and 134 both in the user/listbox.c). Got same results here. Every emulated OS passes except win31.
Good! I'm glad its not just me ...
Also, does anyone else get orphaned zombie processes after running the regression tests? (which is moderately impressive: I thought init was supposed to clean these up)
I get some zombies too, and the kernel notices it. This is what I have in /var/log/messages: Oct 30 10:44:18 wine kernel: application bug: wine(2120) has SIGCHLD set to SIG_IGN but calls wait(). Oct 30 10:44:18 wine kernel: (see the NOTES section of 'man 2 wait'). Workaround activated.
That's interesting. My syslog doesn't have any message like that. What kernel are you running? I'm using 2.6.0-test8 on quisquiliae.
Talking about the kernel process test, it seems they are runned more than once, is it the normal way ? ../../../tools/runtest -q -P wine -M kernel32.dll -T ../../.. -p kernel32_test.exe.so process.c && touch process.ok tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. [12 idential lines follow]
Yep, I get that (except I get 14 lines in total) when I take the -q option out. Cheers, Paul. ---- Paul Millar
~/.wine/config would be good. Attached.
That's interesting. My syslog doesn't have any message like that. What kernel are you running? I'm using 2.6.0-test8 on quisquiliae. It seems Im using kernel 2.4.20-20.9 (redhat 9 rpm) here.
Yep, I get that (except I get 14 lines in total) when I take the -q option out.
===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 Say NO to software patents Dites NON aux brevets logiciels "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
Also, does anyone else get orphaned zombie processes after running the regression tests? (which is moderately impressive: I thought init was supposed to clean these up)
The execution of the attached script in dlls/ shows the only dll test which generates orphaned zombies is kernel. The result I have it with my script is : (had the same result with another kernel) ... ./imm32 ./imm32 : 3 zombies ./kernel ./kernel : 4 zombies ... Paul, Sami, (and perhaps others), could you run this script and send me the results ? Paul, could you say more about this one?
I get about six zombies per regression test. I tracked one of these zombies down to the kernel/test/process.c test_DebuggingFlag()'s ContinueDebugEvent() call, which disappears into wineserver.
===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 Say NO to software patents Dites NON aux brevets logiciels "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
On Sat, 8 Nov 2003, [iso-8859-1] Sylvain Petreolle wrote:
The execution of the attached script in dlls/ shows the only dll test which generates orphaned zombies is kernel.
Actually shows the cumulative total. I took the liberty of hacking it a bit. See http://www.astro.gla.ac.uk/users/paulm/Scripts/zombtest [...]
Paul, Sami, (and perhaps others), could you run this script and send me the results ?
OK, here's the result of some investigations: o On lilith (RH-7.3, gcc-2.96, glibc-2.2.5-43, 2.4.20 kernel) *no* zombies are generated for the conformance tests. o On quisquiliae (RH-7.3, gcc-3.2.1, glibc-2.2.5-43, 2.6.0-test8 kernel) a single zombie is created, which happens when the kernel DLL tests are run. o Copying the whole lilith-compiled wine tree across to quisquiliae and re-running zombtest, I get a zombie. Looks suspiciously like the 2.6.0-test8 kernel is to blame. To confirm this, I rebooted quisquiliae using a 2.4.20-kernel. Guess what? No zombies.
Paul, could you say more about this one?
I get about six zombies per regression test. I tracked one of these zombies down to the kernel/test/process.c test_DebuggingFlag()'s ContinueDebugEvent() call, which disappears into wineserver.
Not that much more. Originally, when running the full gamut of conformance tests on my laptop (which is running 2.6.0-test9), six zombies orphan processes were created. One of these zombies was created when running the kernel DLL tests (the one that is created when running 2.6.0-test8). I tracked the problem down to tests/process.c line 967: ContinueDebugEvent(de.dwProcessId, de.dwThreadId, DBG_CONTINUE);
From memory, it was the second (but not the final) time around the loop that the zombie appeared.
I tried to trace this into the wine itself, but unfortunately ran out of free time :( ---- Paul Millar
From: "Paul Millar" <paulm(a)astro.gla.ac.uk> To: <spetreolle(a)users.sourceforge.net> Cc: "Sami Aario" <sami.aario(a)surfeu.fi>; <wine-devel(a)winehq.org> Sent: Tuesday, November 11, 2003 12:56 PM Subject: Re: Zombies (was : Conformance tests...)
Looks suspiciously like the 2.6.0-test8 kernel is to blame. To confirm this, I rebooted quisquiliae using a 2.4.20-kernel. Guess what? No zombies.
My kernel is the Debian sarge default kernel, 2.2.20. I get zero zombies.
From: "Sylvain Petreolle" <spetreolle(a)yahoo.fr> To: "Paul Millar" <paulm(a)astro.gla.ac.uk>; <spetreolle(a)users.sourceforge.net> Cc: "Sami Aario" <sami.aario(a)surfeu.fi>; <wine-devel(a)winehq.org> Sent: Saturday, November 08, 2003 3:17 PM Subject: Zombies (was : Conformance tests...)
Paul, Sami, (and perhaps others), could you run this script and send me the results ?
Results attached.
participants (3)
-
Paul Millar -
Sami Aario -
Sylvain Petreolle