On 9/20/21 11:03 AM, Marvin wrote:
Hi,
While running your changed tests, 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: https://testbot.winehq.org/JobDetails.pl?Key=98315
Your paranoid android.
=== debiant2 (32 bit report) ===
dinput8: hid.c:4105: Test succeeded inside todo block: got dwSequence 0xa, expected 0xa hid.c:4117: Test succeeded inside todo block: objdata[0]: got dwSequence 0xa, expected 0xa hid.c:4117: Test succeeded inside todo block: objdata[1]: got dwSequence 0xa, expected 0xa hid.c:4117: Test succeeded inside todo block: objdata[2]: got dwSequence 0xa, expected 0xa hid.c:4117: Test succeeded inside todo block: objdata[3]: got dwSequence 0xa, expected 0xa
=== debiant2 (64 bit WoW report) ===
dinput8: hid.c:4105: Test succeeded inside todo block: got dwSequence 0xa, expected 0xa hid.c:4117: Test succeeded inside todo block: objdata[0]: got dwSequence 0xa, expected 0xa hid.c:4117: Test succeeded inside todo block: objdata[1]: got dwSequence 0xa, expected 0xa hid.c:4117: Test succeeded inside todo block: objdata[2]: got dwSequence 0xa, expected 0xa hid.c:4117: Test succeeded inside todo block: objdata[3]: got dwSequence 0xa, expected 0xa
I should probably just remove these sequence number tests, it's not very useful and it fails from time to time. It's not related to these patches though.