Re: [PATCH 4/5] secur32: Perform TLS handshake even if input is empty.

[Rémi Bernon]

On 2/15/21 1:22 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=85600
>
> Your paranoid android.
>
> === debiant2 (32 bit report) ===
>
> secur32:
> schannel.c:818: Test failed: Output buffer size changed.
> schannel.c:833: Test failed: Output buffer size changed.
> schannel.c:842: Test failed: Output buffer size changed.
> schannel: Timeout
>
> === debiant2 (32 bit Chinese:China report) ===
>
> secur32:
> schannel.c:818: Test failed: Output buffer size changed.
> schannel.c:833: Test failed: Output buffer size changed.
> schannel.c:842: Test failed: Output buffer size changed.
> schannel: Timeout
>
> === debiant2 (32 bit WoW report) ===
>
> secur32:
> schannel.c:818: Test failed: Output buffer size changed.
> schannel.c:833: Test failed: Output buffer size changed.
> schannel.c:842: Test failed: Output buffer size changed.
> schannel: Timeout
>
> === debiant2 (64 bit WoW report) ===
>
> secur32:
> schannel.c:818: Test failed: Output buffer size changed.
> schannel.c:833: Test failed: Output buffer size changed.
> schannel.c:842: Test failed: Output buffer size changed.
> schannel: Timeout

I guess that speaks for itself, but I'm still interested to discuss how 
to properly test the re-handshake, if there are ways.