Re: [PATCH 4/8] server: send the proper status code in case of socket error

[Greg Geldorp]

Hi,

While running your changed tests on Windows, 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
http://testbot.winehq.org/JobDetails.pl?Key=1520

Your paranoid android.


=== W7PROX64 (Windows 7 Professional 64 bit) ===
sock.c:3162: Test failed: Expected event sequence [FD_OOB(0) bad(65)], got [FD_OOB(0)]

[PATCH 4/8] server: send the proper status code in case of socket error

[Mike Kaplinskiy]

On Sun, Apr 18, 2010 at 4:00 AM, Greg Geldorp <ggeldorp(a)vmware.com> wrote:
> Hi,
>
> While running your changed tests on Windows, 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
> http://testbot.winehq.org/JobDetails.pl?Key=1520
>
> Your paranoid android.
>
> === W7PROX64 (Windows 7 Professional 64 bit) ===
> sock.c:3162: Test failed: Expected event sequence [FD_OOB(0) bad(65)], got [FD_OOB(0)]

Oooh 64 bit tests. Shiny. Looks like it's easier to catch pointer
mistakes on 64 bit, forgot to 0 terminate a sequence. Will resend a
new try :)

Mike.