Re: [PATCH 3/5] msvcrt: Support NULL buffer in setvbuf

[Marvin]

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
https://testbot.winehq.org/JobDetails.pl?Key=7709

Your paranoid android.

=== build (build) ===
Patch failed to apply

[PATCH 3/5] msvcrt: Support NULL buffer in setvbuf

[Piotr Caban]

On 06/26/14 12:31, Marvin 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
> https://testbot.winehq.org/JobDetails.pl?Key=7709
>
> Your paranoid android.
>
> === build (build) ===
> Patch failed to apply

Testbot failed to update wine source yesterday.

[PATCH 3/5] msvcrt: Support NULL buffer in setvbuf

[Francois Gouget]

On Thu, 26 Jun 2014, Piotr Caban wrote:
[...]
> Testbot failed to update wine source yesterday.

For whatever reason the build VM's disk image became corrupted. This is 
why it suddenly got a Perl error in an unchanged Perl script. It also 
had a bunch of other errors with many tools like ls not working anymore.

So time morning I restored the disk image from backup and now it appears 
to be working fine again.

I'm keeping the broken disk image around in case someone's interested in 
doing some forensic analysis to figure out what happened (I checked that 
the file could be read without trouble so it's not an issue in the 
host's disk). However given that the VM host still runs the 3.2.0 kernel 
(to avoid further instability in newer kernels ironically), it may not 
be very fruitful.