Flaky test update

[Dan Kegel]

On Wed, Sep 24, 2008 at 7:04 AM, Dan Kegel <dank at kegel.com> wrote:
> Two tests usually failed:
>
> user32:msg.c 940
> user32:input.c 756

And here's histogram of first error message in the user32:input.c failures:
    156 user32:input.c:740: Test failed: a4/0: the msg sequence is not
complete: expected 0000 - actual 0046
    103 user32:input.c:662: Test failed: 01: 12 from 81 -> 01 unexpected
     90 user32:input.c:718: Test failed: 46/0: the msg 0x0106 was
expected, but got msg 0x0046 instead
     67 user32:input.c:740: Test failed: 46/0: the msg sequence is not
complete: expected 0000 - actual 0046
     65 user32:input.c:646: Test failed: 00: 12 from 00 -> 00 instead
of 00 -> 80
     21 user32:input.c:718: Test failed: 41/0: the msg 0x0100 was
expected, but got msg 0x0046 instead
     13 user32:input.c:718: Test failed: 46/0: the msg 0x0104 was
expected, but got msg 0x0046 instead
     11 user32:input.c:718: Test failed: a2/0: the msg 0x0100 was
expected, but got msg 0x0046 instead
      9 user32:input.c:718: Test failed: a4/2: the msg 0x0101 was
expected, but got msg 0x0046 instead
      8 user32:input.c:740: Test failed: a2/0: the msg sequence is not
complete: expected 0000 - actual 0046

That system doesn't even *have* a mouse, so it wasn't mouse motion.

As a reality check, I verified that it failed on a
different system, idle, with no user apps and
no user mouse or keyboard events.
When run in a loop it failed after 75 runs; the first error was

input.c:648: Test failed: 00: 12 from 00 -> 00 instead of 00 -> 80