From: Marvin Subject: Re: [PATCH v3] ws2_32: Handle more IGMP socket options Message-Id: Date: Fri, 18 Oct 2019 12:38:39 -0500 In-Reply-To: <20191018173253.4274-1-dark.shadow4@web.de> References: <20191018173253.4274-1-dark.shadow4@web.de> 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=57992 Your paranoid android. === debian10 (32 bit report) === ws2_32: sock.c:3058: Test succeeded inside todo block: Test[1]: expected 0, got 0 sock.c:3058: Test succeeded inside todo block: Test[2]: expected 0, got 0 sock.c:3058: Test succeeded inside todo block: Test[1]: expected 0, got 0 sock.c:3058: Test succeeded inside todo block: Test[2]: expected 0, got 0 === debian10 (32 bit Chinese:China report) === ws2_32: sock.c:3052: Test failed: Test[1]: expected 2, got 0 sock.c:3052: Test failed: Test[2]: expected 2, got 0 sock.c:3052: Test failed: Test[1]: expected 2, got 0 sock.c:3052: Test failed: Test[2]: expected 2, got 0 === debian10 (32 bit WoW report) === ws2_32: sock.c:3058: Test succeeded inside todo block: Test[1]: expected 0, got 0 sock.c:3058: Test succeeded inside todo block: Test[2]: expected 0, got 0 sock.c:3058: Test succeeded inside todo block: Test[2]: expected 0, got 0 sock.c:3058: Test succeeded inside todo block: Test[2]: expected 0, got 0