[PATCH] kernel32/tests: A couple of spelling fixes in ok() call messages.

[Francois Gouget]

Signed-off-by: Francois Gouget 
---
 dlls/kernel32/tests/debugger.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dlls/kernel32/tests/debugger.c b/dlls/kernel32/tests/debugger.c
index 106c1c4e0e4..548ef0be395 100644
--- a/dlls/kernel32/tests/debugger.c
+++ b/dlls/kernel32/tests/debugger.c
@@ -329,7 +329,7 @@ static void process_attach_events(struct debugger_context *ctx)
     ok(ctx->ev.dwDebugEventCode == EXCEPTION_DEBUG_EVENT, "dwDebugEventCode = %d\n", ctx->ev.dwDebugEventCode);
     ok(ctx->ev.u.Exception.ExceptionRecord.ExceptionCode == EXCEPTION_BREAKPOINT, "ExceptionCode = %x\n",
        ctx->ev.u.Exception.ExceptionRecord.ExceptionCode);
-    ok(ctx->ev.u.Exception.ExceptionRecord.ExceptionAddress == pDbgBreakPoint, "ExceptionAddres != DbgBreakPoint\n");
+    ok(ctx->ev.u.Exception.ExceptionRecord.ExceptionAddress == pDbgBreakPoint, "ExceptionAddress != DbgBreakPoint\n");

/* flush debug events */
     do next_event(ctx, POLL_EVENT_TIMEOUT);
@@ -1006,7 +1006,7 @@ static void test_debug_children(char *name, DWORD flag, BOOL debug_child)
         ok(ctx.ev.dwThreadId == last_thread, "unexpected thread\n");
         ok(ctx.ev.u.Exception.ExceptionRecord.ExceptionCode == EXCEPTION_BREAKPOINT, "ExceptionCode = %x\n",
            ctx.ev.u.Exception.ExceptionRecord.ExceptionCode);
-        ok(ctx.ev.u.Exception.ExceptionRecord.ExceptionAddress == pDbgBreakPoint, "ExceptionAddres != DbgBreakPoint\n");
+        ok(ctx.ev.u.Exception.ExceptionRecord.ExceptionAddress == pDbgBreakPoint, "ExceptionAddress != DbgBreakPoint\n");

ret = SetEvent(event_attach);
         ok(ret, "SetEvent failed, last error %d.\n", GetLastError());

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

Your paranoid android.

=== wvistau64 (task log) ===

Task errors:
The task timed out

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

kernel32:
debugger: Timeout

=== w7pro64 (64 bit report) ===

kernel32:
debugger: Timeout

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

kernel32:
debugger: Timeout

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

kernel32:
debugger: Timeout

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

kernel32:
debugger: Timeout

=== debian10 (32 bit report) ===

kernel32:
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00438184).

=== debian10 (32 bit French report) ===

kernel32:
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00438184).

=== debian10 (32 bit Japanese:Japan report) ===

kernel32:
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00438184).

=== debian10 (32 bit Chinese:China report) ===

kernel32:
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00438184).

=== debian10 (32 bit WoW report) ===

kernel32:
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00438184).

=== debian10 (64 bit WoW report) ===

kernel32:
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x00438184).