[PATCH] user32/tests: Fix the keyboard layout id in an ok() message.

[Francois Gouget]

The keyboard layout being tested is not the thread's default keyboard
layout.

Signed-off-by: Francois Gouget 
---
See also https://bugs.winehq.org/show_bug.cgi?id=51478

dlls/user32/tests/input.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dlls/user32/tests/input.c b/dlls/user32/tests/input.c
index 654cabb76d9..08323c4f40e 100644
--- a/dlls/user32/tests/input.c
+++ b/dlls/user32/tests/input.c
@@ -3166,7 +3166,7 @@ static void test_keyboard_layout_name(void)
             swprintf( tmpklid, KL_NAMELENGTH, L"%08X", layouts_preload[j] );
             if (!wcscmp( tmpklid, klid )) break;
         }
-        ok(j < len, "Could not find keyboard layout %p in preload list\n", layout);
+        ok(j < len, "Could not find keyboard layout %s in preload list\n", wine_dbgstr_w(klid));

if (id & 0x80000000)
         {

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

Your paranoid android.

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

user32:
input.c:2341: Test failed: Spurious WM_INPUT messages

=== wvistau64 (64 bit report) ===

user32:
input.c:757: Test failed:  0 (a4/0): 01 from 01 -> 00 unexpected
input.c:757: Test failed:  0 (a4/0): 11 from 01 -> 00 unexpected
input.c:757: Test failed:  0 (a4/0): a2 from 01 -> 00 unexpected

=== w10pro64 (64 bit report) ===

user32:
input.c:1303: Test failed: Wrong set pos: (100,100)
input.c:1323: Test failed: GetCursorPos: (100,100)