Re: kernel32: Clamp maximum console window size to screen buffer size.

[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=19420

Your paranoid android.


=== w8 (32 bit console) ===
console.c:1445: Test failed: [13] Expected output count to be 0, got 2359244
console.c:1445: Test failed: [15] Expected output count to be 0, got 2359244
console.c:1445: Test failed: [18] Expected output count to be 3735928559, got 2359244
console.c:1689: Test failed: [13] Expected output count to be 0, got 2359244
console.c:1689: Test failed: [15] Expected output count to be 0, got 2359244
console.c:1689: Test failed: [18] Expected output count to be 3735928559, got 2359244

=== w864 (32 bit console) ===
console.c:1445: Test failed: [13] Expected output count to be 0, got 2686924
console.c:1445: Test failed: [15] Expected output count to be 0, got 2686924
console.c:1445: Test failed: [18] Expected output count to be 3735928559, got 2686924
console.c:1689: Test failed: [13] Expected output count to be 0, got 2686924
console.c:1689: Test failed: [15] Expected output count to be 0, got 2686924
console.c:1689: Test failed: [18] Expected output count to be 3735928559, got 2686924

=== w1064 (32 bit console) ===
console.c:2567: Test failed: expected ERROR_INVALID_HANDLE, got 1
console.c:2573: Test failed: expected ERROR_NOT_ENOUGH_MEMORY, got 998
console.c:2580: Test failed: expected ERROR_NOT_ENOUGH_MEMORY, got 998
console.c:2587: Test failed: expected ERROR_NOT_ENOUGH_MEMORY, got 998
console.c:1270: Test failed: expected VerifyConsoleIoHandle to succeed
console.c:1445: Test failed: [3] Expected output count to be 3735928559, got 0
console.c:1445: Test failed: [11] Expected output count to be 3735928559, got 0
console.c:1445: Test failed: [13] Expected output count to be 0, got 2752460
console.c:1445: Test failed: [15] Expected output count to be 0, got 2752460
console.c:1445: Test failed: [18] Expected output count to be 3735928559, got 2752460
console.c:1689: Test failed: [3] Expected output count to be 3735928559, got 0
console.c:1689: Test failed: [11] Expected output count to be 3735928559, got 0
console.c:1689: Test failed: [13] Expected output count to be 0, got 2752460
console.c:1689: Test failed: [15] Expected output count to be 0, got 2752460
console.c:1689: Test failed: [18] Expected output count to be 3735928559, got 2752460
console.c:2148: Test failed: [7] Expected count to be 0, got 1
console.c:2214: Test failed: [7] Expected count to be 0, got 1
console.c:2280: Test failed: [7] Expected count to be 0, got 1

kernel32: Clamp maximum console window size to screen buffer size.

[Sebastian Lackner]

On 06.01.2016 02:05, 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=19420
>
> Your paranoid android.
>
> === w8 (32 bit console) ===
> console.c:1445: Test failed: [13] Expected output count to be 0, got 2359244
> console.c:1445: Test failed: [15] Expected output count to be 0, got 2359244
> console.c:1445: Test failed: [18] Expected output count to be 3735928559, got 2359244
> console.c:1689: Test failed: [13] Expected output count to be 0, got 2359244
> console.c:1689: Test failed: [15] Expected output count to be 0, got 2359244
> console.c:1689: Test failed: [18] Expected output count to be 3735928559, got 2359244
>
> === w864 (32 bit console) ===
> console.c:1445: Test failed: [13] Expected output count to be 0, got 2686924
> console.c:1445: Test failed: [15] Expected output count to be 0, got 2686924
> console.c:1445: Test failed: [18] Expected output count to be 3735928559, got 2686924
> console.c:1689: Test failed: [13] Expected output count to be 0, got 2686924
> console.c:1689: Test failed: [15] Expected output count to be 0, got 2686924
> console.c:1689: Test failed: [18] Expected output count to be 3735928559, got 2686924
>
> === w1064 (32 bit console) ===
> console.c:2567: Test failed: expected ERROR_INVALID_HANDLE, got 1
> console.c:2573: Test failed: expected ERROR_NOT_ENOUGH_MEMORY, got 998
> console.c:2580: Test failed: expected ERROR_NOT_ENOUGH_MEMORY, got 998
> console.c:2587: Test failed: expected ERROR_NOT_ENOUGH_MEMORY, got 998
> console.c:1270: Test failed: expected VerifyConsoleIoHandle to succeed
> console.c:1445: Test failed: [3] Expected output count to be 3735928559, got 0
> console.c:1445: Test failed: [11] Expected output count to be 3735928559, got 0
> console.c:1445: Test failed: [13] Expected output count to be 0, got 2752460
> console.c:1445: Test failed: [15] Expected output count to be 0, got 2752460
> console.c:1445: Test failed: [18] Expected output count to be 3735928559, got 2752460
> console.c:1689: Test failed: [3] Expected output count to be 3735928559, got 0
> console.c:1689: Test failed: [11] Expected output count to be 3735928559, got 0
> console.c:1689: Test failed: [13] Expected output count to be 0, got 2752460
> console.c:1689: Test failed: [15] Expected output count to be 0, got 2752460
> console.c:1689: Test failed: [18] Expected output count to be 3735928559, got 2752460
> console.c:2148: Test failed: [7] Expected count to be 0, got 1
> console.c:2214: Test failed: [7] Expected count to be 0, got 1
> console.c:2280: Test failed: [7] Expected count to be 0, got 1

Those are preexisting failures.