Re: [PATCH 5/6] winmm/tests: MCI_STATUS returns DWORD_PTR, unlike other commands.

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=4901

Your paranoid android.

=== W98SE (32 bit mci) ===
mci.c:714: Test failed: Expect message 0001 from play to 250 wait notify
mci.c:721: Test failed: got 0004 instead of MCI_NOTIFY_xyz 0000 from command after close
mci.c:782: Test failed: not enough time elapsed 58ms
mci.c:838: Test failed: mci status position: 58

[PATCH 5/6] winmm/tests: MCI_STATUS returns DWORD_PTR, unlike other commands.

Hi,
> Your paranoid android.
> mci.c:714: Test failed: Expect message 0001 from play to 250 wait notify
> mci.c:721: Test failed: got 0004 instead of MCI_NOTIFY_xyz 0000 from command after close
> mci.c:782: Test failed: not enough time elapsed 58ms
> mci.c:838: Test failed: mci status position: 58

Sadly, that's the well-known transient flakyness that I blame on
vmware's timers (or perhaps native bugs?).

Did anybody with a real machine ever get any similar failures?
That would be more revealing to analyse.

Regards,
 Jörg Höhle