http://bugs.winehq.org/show_bug.cgi?id=29094
Bug #: 29094 Summary: d3dx8/device.c, d3dx9/device.c: sometimes fails with "Test failed: Didn't receive MOUSEMOVE" Product: Wine Version: 1.3.31 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: dank@kegel.com Classification: Unclassified
I've seen runs of errors like this on my i7 / ubuntu 11.10 system (nvidia geforce 8500 gt, 270.41.06)
device.c:895: Test failed: Didn't receive MOUSEMOVE 2 (100, 100). alarum: fail: exit status 1, command '../../../wine d3d8_test.exe.so device.c ' device.c:3239: Test failed: Didn't receive MOUSEMOVE 5 (125, 125). alarum: fail: exit status 1, command '../../../wine d3d9_test.exe.so device.c '
Examples:
http://www.winehq.org/pipermail/wine-tests-results/2011-October/005109.html http://www.winehq.org/pipermail/wine-tests-results/2011-October/005110.html http://www.winehq.org/pipermail/wine-tests-results/2011-October/005111.html http://www.winehq.org/pipermail/wine-tests-results/2011-October/005112.html http://www.winehq.org/pipermail/wine-tests-results/2011-November/005187.html
Since the failure seems to happen both in d3d8 and d3d9, it doesn't seem flaky in the usual way. (I should probably start reporting system uptime in the test failure logs.) The uptime at the most recent error was 6 days.
FWIW, the first revision this was seen with was 7df024529541128719ed09a7ed69bda0b11beadb but I have no idea if it's a regression.