On 6/3/21 10:17 PM, 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=91854
Your paranoid android.
=== debiant2 (32 bit report) ===
ws2_32: sock.c:3629: Test failed: bind failed with 10022 sock.c:3632: Test failed: getsockname failed with 10022 sock.c:3634: Test failed: address does not match: 0.0.0.0 != 10.42.42.150
=== debiant2 (32 bit Chinese:China report) ===
ws2_32: sock.c:3629: Test failed: bind failed with 10022 sock.c:3632: Test failed: getsockname failed with 10022 sock.c:3634: Test failed: address does not match: 0.0.0.0 != 10.42.42.150
=== debiant2 (32 bit WoW report) ===
ws2_32: sock.c:3629: Test failed: bind failed with 10022 sock.c:3632: Test failed: getsockname failed with 10022 sock.c:3634: Test failed: address does not match: 0.0.0.0 != 10.42.42.150
This error message seems to be legitimate; please do not commit any but the 1st patch in this series.