joerg-cyril.hoe...@t-systems.com writes:
> What do you suggest?
> a) remove if(winetest...) and always execute the average test
> - Live with occasional failures when the Linux scheduler decides so.
>(This is not unlike audio glitches when sometimes, Linux wakes up a thread
> after 100ms onl
Hi,
>sometimes one DeleteTimerQueueTimer(INVALID_HANDLE_VALUE)
>fails (presumably with IO_PENDING) because a callback was executing
>concurrently.
This random failure rose an alarm. I looked at it further and found out that
the current testsuite is not complete enough to demonstrate that given
IN
joerg-cyril.hoe...@t-systems.com writes:
> I've been using
> if (winetest_debug > 0)
> partly because the trace output in a Gnome-terminal slows down wine such that
> the tests fail
> -- redirect output to a file and the problem goes away (testbot does this) --
> and partly because make -j can ca
On Wed, Mar 14, 2012 at 05:32, wrote:
> Hi,
>
> this should have been labeled [PATCH 3/3] because tests will fail without my
> 2 ntdll patches.
>
> First a note unrelated to my patches: if you run the tests in git in a loop,
> sometimes one DeleteTimerQueueTimer(INVALID_HANDLE_VALUE)
> fails (pr
