5 Nov
2022
5 Nov
'22
10:35 a.m.
On Sat Nov 5 09:49:23 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=125803 Your paranoid android. === debian11 (32 bit report) === wininet: http.c:634: Test failed: Expected position 0xffffffff. Got 0xffffffff. GetLastError() 131 === debian11 (32 bit ar:MA report) === wininet: http.c:634: Test failed: Expected position 0xffffffff. Got 0xffffffff. GetLastError() 131 === debian11 (32 bit de report) === wininet: http.c:634: Test failed: Expected position 0xffffffff. Got 0xffffffff. GetLastError() 131 === debian11 (32 bit zh:CN report) === wininet: http.c:634: Test failed: Expected position 0xffffffff. Got 0xffffffff. GetLastError() 131
Should I be concerned with this report? Does that mean the test will pass on actual 32-bit windows, but not on 32-bit debian?