Hi Dmitry,
--- Dmitry Timoshkov <[EMAIL PROTECTED]> wrote:
> Does moving flush_events() a bit further like in the attached patch
> help?
It seems to help a bit, it fails about 50% of the time just by moving it.
> If it doesn't, please try to change 100 in flush_events to 200 or even
> more and s
"Juan Lang" <[EMAIL PROTECTED]> wrote:
win.c:2414: Test failed: message 000f available
win.c:2422: Test failed: message 000f available
win.c:2430: Test failed: message 000f available
make: *** [win.ok] Error 3
On the fourth run it succeeded. I know you know that these are WM_PAINT
again.
Doe
--- Dmitry Timoshkov <[EMAIL PROTECTED]> wrote:
> 0x200 is WM_MOUSEMOVE. So it's that you either moving the mouse
> during the test, or there is some other source of that message.
> Juan, you need to investigate what is going on if that's the latter.
This appears to be a Heisenbug. I ran the test
--- Dmitry Timoshkov <[EMAIL PROTECTED]> wrote:
> 0x200 is WM_MOUSEMOVE. So it's that you either moving the mouse
> during the test, or there is some other source of that message.
> Juan, you need to investigate what is going on if that's the latter.
Yes, I know. My mouse is a builtin touchpad (o
"Juan Lang" <[EMAIL PROTECTED]> wrote:
Not sure. I get a similar failure on an earlier line:
win.c:2508: Test failed: message 0200 available
This is the repeated failure after rerunning the tests several times to
get past earlier intermittent failures.
0x200 is WM_MOUSEMOVE. So it's that you
> No it's not correct. Does the attached patch fix the failure?
Not sure. I get a similar failure on an earlier line:
win.c:2508: Test failed: message 0200 available
This is the repeated failure after rerunning the tests several times to
get past earlier intermittent failures.
--Juan
_
"Juan Lang" <[EMAIL PROTECTED]> wrote:
The attached patch (sorry, crappy mailer) fixes the win.c failure I was
seeing. Is it correct?
No it's not correct. Does the attached patch fix the failure?
--
Dmitry.
--- cvs/hq/wine/dlls/user/tests/win.c 2006-08-05 15:05:54.0 +0900
+++ wine/
The attached patch (sorry, crappy mailer) fixes the win.c failure I was
seeing. Is it correct?
--Juan
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com Index: dlls/user/tests/win.c
