Re: [PATCH v2 2/2] kernelbase: Implement SetConsoleScreenBufferInfoEx().

[Marvin]

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=66204

Your paranoid android.

=== w2008s64 (32 bit report) ===

kernel32:
console.c:3165: Test failed: got 87, expected 6
console.c:3169: Test failed: got 0, expected one
console.c:3170: Test failed: got 87, expected 0xdeadbeef
console.c:3175: Test failed: got 87, expected 5 or 6

=== w8 (32 bit report) ===

kernel32:
console.c:3165: Test failed: got 87, expected 6
console.c:3169: Test failed: got 0, expected one
console.c:3170: Test failed: got 87, expected 0xdeadbeef
console.c:3175: Test failed: got 87, expected 5 or 6

=== w8adm (32 bit report) ===

kernel32:
console.c:3165: Test failed: got 87, expected 6
console.c:3169: Test failed: got 0, expected one
console.c:3170: Test failed: got 87, expected 0xdeadbeef
console.c:3175: Test failed: got 87, expected 5 or 6

=== w864 (32 bit report) ===

kernel32:
console.c:3165: Test failed: got 87, expected 6
console.c:3169: Test failed: got 0, expected one
console.c:3170: Test failed: got 87, expected 0xdeadbeef
console.c:3175: Test failed: got 87, expected 5 or 6

=== w1064v1507 (32 bit report) ===

kernel32:
console.c:3165: Test failed: got 87, expected 6
console.c:3169: Test failed: got 0, expected one
console.c:3170: Test failed: got 87, expected 0xdeadbeef
console.c:3175: Test failed: got 87, expected 5 or 6

=== w1064v1809 (32 bit report) ===

kernel32:
console.c:3169: Test failed: got 0, expected one
console.c:3170: Test failed: got 87, expected 0xdeadbeef

=== w1064v1809_2scr (32 bit report) ===

kernel32:
console.c:3169: Test failed: got 0, expected one
console.c:3170: Test failed: got 87, expected 0xdeadbeef

=== w1064v1809_ar (32 bit report) ===

kernel32:
console.c:3169: Test failed: got 0, expected one
console.c:3170: Test failed: got 87, expected 0xdeadbeef

=== w1064v1809_he (32 bit report) ===

kernel32:
console.c:3169: Test failed: got 0, expected one
console.c:3170: Test failed: got 87, expected 0xdeadbeef

=== w1064v1809_ja (32 bit report) ===

kernel32:
console.c:3169: Test failed: got 0, expected one
console.c:3170: Test failed: got 87, expected 0xdeadbeef

=== w1064v1809_zh_CN (32 bit report) ===

kernel32:
console.c:3169: Test failed: got 0, expected one
console.c:3170: Test failed: got 87, expected 0xdeadbeef

=== w2008s64 (64 bit report) ===

kernel32:
console.c:3165: Test failed: got 87, expected 6
console.c:3169: Test failed: got 0, expected one
console.c:3170: Test failed: got 87, expected 0xdeadbeef
console.c:3175: Test failed: got 87, expected 5 or 6

=== w864 (64 bit report) ===

kernel32:
console.c:3165: Test failed: got 87, expected 6
console.c:3169: Test failed: got 0, expected one
console.c:3170: Test failed: got 87, expected 0xdeadbeef
console.c:3175: Test failed: got 87, expected 5 or 6

=== w1064v1507 (64 bit report) ===

kernel32:
console.c:3165: Test failed: got 87, expected 6
console.c:3169: Test failed: got 0, expected one
console.c:3170: Test failed: got 87, expected 0xdeadbeef
console.c:3175: Test failed: got 87, expected 5 or 6

=== w1064v1809 (64 bit report) ===

kernel32:
console.c:3169: Test failed: got 0, expected one
console.c:3170: Test failed: got 87, expected 0xdeadbeef