[PATCH 1/2] wininet: Free Critical Section (valrind)

Alistair Leslie-Hughes leslie_alistair at hotmail.com
Tue Nov 10 23:24:55 CST 2015


No caused by this patch.

On 11/11/15 14:52, 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=18101
>
> Your paranoid android.
>
>
> === w1064 (32 bit http) ===
> http.c:534: Test failed: HTTP_QUERY_RAW_HEADERS: expected length 0, but got 1
> http.c:534: Test failed: HTTP_QUERY_RAW_HEADERS: expected length 0, but got 1
> http.c:534: Test failed: HTTP_QUERY_RAW_HEADERS: expected length 0, but got 1
> http.c:534: Test failed: HTTP_QUERY_RAW_HEADERS: expected length 0, but got 1
> http.c:534: Test failed: HTTP_QUERY_RAW_HEADERS: expected length 0, but got 1
> http.c:1773: Test failed: Expected 2, got 4
> http.c:1774: Test failed: Expected CRLF, got '
> http.c:2408: Test failed: count was wrong
> http.c:2409: Test failed: http data wrong, got: Garbage: Header
> http.c:3072: Test failed: HttpAddRequestHeaders succeeded
> http.c:3073: Test failed: Expected error ERROR_HTTP_HEADER_NOT_FOUND, got 0
> http.c:3078: Test failed: code = 200, expected 400
> http.c:3078: Test failed: code = 200, expected 400
> http.c:3078: Test failed: unexpected status code 200, expected 400
> http.c:3078: Test failed: unexpected status code 200, expected 400
> http.c:534: Test failed: HTTP_QUERY_RAW_HEADERS: expected length 0, but got 1
>
>
>




More information about the wine-devel mailing list