7 Dec
2022
7 Dec
'22
4:13 a.m.
On Wed Dec 7 02:11:09 2022 +0000, **** wrote:
Marvin replied on the mailing list:
Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=127287 Your paranoid android. === w10pro64 (32 bit report) === cryptowinrt: crypto.c:281: Test failed: got status 0 crypto.c:281: Test failed: GetResults returned 0x8000000e crypto.c:296: Test failed: handler not invoked crypto.c:297: Test failed: got async 00000000 crypto.c:298: Test failed: got status 0 crypto.c:301: Test failed: got handler 0063FC60 crypto.c:305: Test failed: handler invoked crypto.c:306: Test failed: got async 009724A0 crypto.c:307: Test failed: got status 1 === debian11 (32 bit report) === winhttp: notification.c:122: Test failed: 943: expected callback to be called from the same thread notification.c:122: Test failed: 948: expected callback to be called from the same thread notification.c:122: Test failed: 953: expected callback to be called from the same thread notification.c:997: Test failed: got 4 notification.c:1006: Test failed: got 0 notification.c:1010: Test failed: unexpected data 0 at 0 notification.c:1017: Test failed: got 0 notification.c:1018: Test failed: got 1002 notification.c:1019: Test failed: got 18 notification.c:1030: Test failed: got 1002 notification.c:122: Test failed: 937: expected callback to be called from the same thread notification.c:122: Test failed: 943: expected callback to be called from the same thread notification.c:122: Test failed: 948: expected callback to be called from the same thread notification.c:122: Test failed: 953: expected callback to be called from the same thread
Hmm, I thought 500 ms would be enough to avoid this issue.