Dan Kegel wrote:
> On Wed, Sep 24, 2008 at 7:04 AM, Dan Kegel <[EMAIL PROTECTED]> wrote:
>> Two tests usually failed:
>>
>> user32:msg.c 940
>> user32:input.c 756
>
> 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
> diffe
On Wed, Sep 24, 2008 at 7:04 AM, Dan Kegel <[EMAIL PROTECTED]> 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: e
Here's some data over 1042 test runs over the last
three weeks, all on a dual core Ubuntu 8.04 linux box with
a cheap nVidia GeForce 8500 GT graphics card.
Three tests crashed from 1% to 10% of the time (as opposed to failed):
ddraw 136
d3d9 48
d3d8 12
Three tests always failed:
urlmon:protoc