Re: kernel32/tests: Test deleting a timer right after creating it.

[Marvin]

Hi,

While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=15671

Your paranoid android.


=== W2KPROSP4 (32 bit sync) ===
sync.c:685: Test failed: DeleteTimerQueueTimer ret=1 le=997

=== WXPPROSP3 (32 bit sync) ===
sync.c:685: Test failed: DeleteTimerQueueTimer ret=1 le=997

=== W2K3R2SESP2 (32 bit sync) ===
sync.c:685: Test failed: DeleteTimerQueueTimer ret=1 le=997

=== WVISTAADM (32 bit sync) ===
sync.c:741: Test failed: Timer callback 0

=== W2K8SE (32 bit sync) ===
sync.c:741: Test failed: Timer callback 0

=== W7PRO (32 bit sync) ===
sync.c:741: Test failed: Timer callback 0

=== W7PROX64 (32 bit sync) ===
sync.c:741: Test failed: Timer callback 0

=== TEST64_W7SP1 (32 bit sync) ===
sync.c:741: Test failed: Timer callback 0

=== W7PROX64 (64 bit sync) ===
sync.c:741: Test failed: Timer callback 0

=== TEST64_W7SP1 (64 bit sync) ===
sync.c:741: Test failed: Timer callback 0