https://bugs.winehq.org/show_bug.cgi?id=54032
Bug ID: 54032 Summary: user32:msg - test_broadcast() sometimes fails due to ERROR_INVALID_PARAMETER on w7pro64 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs@winehq.org Reporter: fgouget@codeweavers.com
user32:msg - test_broadcast() sometimes fails due to ERROR_INVALID_PARAMETER on w7pro64:
msg.c:17400: Test failed: 5: message ffff, got 0, error 87 msg.c:17405: Test failed: 5,0: message ffff, got 0, error 87 msg.c:17405: Test failed: 5,1: message ffff, got 0, error 87 msg.c:17405: Test failed: 5,2: message ffff, got 0, error 87 msg.c:17405: Test failed: 5,3: message ffff, got 0, error 87 msg.c:17405: Test failed: 5,8: message ffff, got 0, error 87 msg.c:17405: Test failed: 5,9: message ffff, got 0, error 87 msg.c:17405: Test failed: 5,10: message ffff, got 0, error 87 msg.c:17405: Test failed: 5,11: message ffff, got 0, error 87 msg.c:17405: Test failed: 5,12: message ffff, got 0, error 87
See https://test.winehq.org/data/patterns.html#user32:msg
Notes: * This is specific to w7pro64 and happens roughly twice a month. * The first known instance dates back to 2022-08-17 and there was none in the 2 months prior. * The w7pro64 snapshot dates back to 2021-08-23.
So the conclusion is that something changed in Wine back in August that causes these failures. Since the logs show no change to that test in that timeframe (the next day does not count), it must be caused by a change in another test :-(
https://bugs.winehq.org/show_bug.cgi?id=54032
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase
https://bugs.winehq.org/show_bug.cgi?id=54032
--- Comment #1 from François Gouget fgouget@codeweavers.com --- This can also happen with the WM_USER, WM_USER+1 and 0xc000 tests, still on Windows 7:
2022-11-28 w7pro64 (64-bit)
msg.c:17400: Test failed: 4: message c000, got 0, error 87 msg.c:17405: Test failed: 4,0: message c000, got 0, error 87 msg.c:17405: Test failed: 4,1: message c000, got 0, error 87 msg.c:17405: Test failed: 4,2: message c000, got 0, error 87 msg.c:17405: Test failed: 4,3: message c000, got 0, error 87 msg.c:17405: Test failed: 4,8: message c000, got 0, error 87
2022-11-10 w7u-el (32-bit)
msg.c:17405: Test failed: 1,11: message 0400, got 0, error 87 msg.c:17405: Test failed: 1,12: message 0400, got 0, error 87 msg.c:17384: Test failed: 2,3: message 0401, got 0, error 87 msg.c:17384: Test failed: 2,8: message 0401, got 0, error 87 msg.c:17384: Test failed: 2,9: message 0401, got 0, error 87 msg.c:17384: Test failed: 2,10: message 0401, got 0, error 87 msg.c:17405: Test failed: 2,0: message 0401, got 0, error 87 msg.c:17405: Test failed: 2,1: message 0401, got 0, error 87 msg.c:17405: Test failed: 2,2: message 0401, got 0, error 87 msg.c:17379: Test failed: 3: message bfff, got 0, error 87
2022-12-15 w7u (32-bit)
msg.c:17379: Test failed: 3: message bfff, got 0, error 87 msg.c:17384: Test failed: 3,0: message bfff, got 0, error 87 msg.c:17384: Test failed: 3,1: message bfff, got 0, error 87 msg.c:17384: Test failed: 3,2: message bfff, got 0, error 87 msg.c:17384: Test failed: 3,3: message bfff, got 0, error 87 msg.c:17384: Test failed: 3,8: message bfff, got 0, error 87 msg.c:17384: Test failed: 3,9: message bfff, got 0, error 87 msg.c:17384: Test failed: 3,10: message bfff, got 0, error 87 msg.c:17384: Test failed: 3,11: message bfff, got 0, error 87 msg.c:17384: Test failed: 3,12: message bfff, got 0, error 87
When the tests for these messages fails the error is always ERROR_INVALID_PARAMETER unlike WM_USER-1 which gets various other errors (see bug 54194).