../../../tools/runtest -q -P wine -M user32.dll -T ../../.. -p user32_test.exe.so msg.c && touch msg.ok fixme:nonclient:NC_HandleSysCommand unimplemented WM_SYSCOMMAND f050! fixme:nonclient:NC_HandleSysCommand unimplemented WM_SYSCOMMAND f040! fixme:nonclient:NC_HandleSysCommand unimplemented WM_SYSCOMMAND f040! fixme:nonclient:NC_HandleSysCommand unimplemented WM_SYSCOMMAND f050! msg.c:5524: Test failed: ScrollWindowEx: the msg 0x000f was expected, but got msg 0x0021 instead msg.c:5524: Test failed: ScrollWindowEx: the msg 0x0014 was expected, but got msg 0x000f instead msg.c:5524: Test failed: ScrollWindowEx: the msg sequence is not complete: expected 0000 - actual 0014 msg.c:3719: Test failed: InvalidateRgn: the msg sequence is not complete: expected 0000 - actual 0021 msg.c:3781: Test failed: WmParentPaintNc: the msg 0x000f was expected, but got msg 0x0021 instead msg.c:3781: Test failed: WmParentPaintNc: the msg 0x000f was expected in child msg.c:3781: Test failed: WmParentPaintNc: the msg 0x0085 was expected, but got msg 0x0014 instead msg.c:3781: Test failed: WmParentPaintNc: the msg 0x0014 was expected, but got msg 0x0021 instead msg.c:3781: Test failed: WmParentPaintNc: the msg sequence is not complete: expected 0000 - actual 000f msg.c:3893: Test failed: WmParentPaintNc2: the msg sequence is not complete: expected 0000 - actual 0021 msg.c:4289: Test failed: Shift+VK_N press/release: the msg 0x0100 was expected, but got msg 0x0021 instead msg.c:4289: Test failed: Shift+VK_N press/release: the msg 0x0100 should have been sent msg.c:4289: Test failed: Shift+VK_N press/release: in msg 0x0100 expecting wParam 0x4e got 0x10 msg.c:4289: Test failed: Shift+VK_N press/release: the msg 0x0100 should have been sent msg.c:4289: Test failed: Shift+VK_N press/release: the msg 0x0100 should have been sent msg.c:4289: Test failed: Shift+VK_N press/release: the msg 0x0102 was expected, but got msg 0x0100 instead msg.c:4289: Test failed: Shift+VK_N press/release: the msg 0x0111 was expected, but got msg 0x0102 instead msg.c:4289: Test failed: Shift+VK_N press/release: the msg 0x0101 was expected, but got msg 0x0111 instead msg.c:4289: Test failed: Shift+VK_N press/release: the msg 0x0101 should have been sent msg.c:4289: Test failed: Shift+VK_N press/release: in msg 0x0101 expecting wParam 0x10 got 0x4e msg.c:4289: Test failed: Shift+VK_N press/release: the msg 0x0101 should have been sent msg.c:4289: Test failed: Shift+VK_N press/release: the msg 0x0101 should have been sent msg.c:4289: Test failed: Shift+VK_N press/release: the msg sequence is not complete: expected 0000 - actual 0101 msg.c:5743: Test failed: WmEmpty: the msg sequence is not complete: expected 0000 - actual 0014
"Uwe" == Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de writes:
Uwe> ../../../tools/runtest -q -P wine -M user32.dll -T ../../.. -p Uwe> user32_test.exe.so msg.c && touch msg.ok .. Uwe> f050! msg.c:5524: Test failed: ScrollWindowEx: the msg 0x000f was Uwe> expected, but got msg 0x0021 instead msg.c:5524: Test failed:
I learned on IRC that this test is very sensitive on any keyboard/mouse interaction. On a single processor machine I really could succeed by "holding my breath" while the test ran. Also the verbose mode (-v) for the tests gave better chances for success.
However on the dual processor machine, the test _never_ succeeded. Only you running "yes > & /dev/null &" so one processor was active made the test succeed.
Bye
-
Uwe Bonnes