[PATCH 0/1] MR5853: user32/tests: Fix spurious "Failed sequence" reports on Windows.

[Esme Povirk (＠madewokherd)]

It turns out that message sequences with "wine_only" messages, although they don't cause a test failure on Windows, do cause `ok_sequence_` to log a failure, so that it dumps the sequence. We need `ok_sequence_` to treat these as skippable messages on Windows so that it ignores the failure to match them.

-- 
https://gitlab.winehq.org/wine/wine/-/merge_requests/5853

[PATCH 1/1] user32/tests: Fix spurious "Failed sequence" reports on Windows.

[Esme Povirk]

From: Esme Povirk <esme(a)codeweavers.com>

---
 dlls/user32/tests/msg.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/dlls/user32/tests/msg.c b/dlls/user32/tests/msg.c
index 71da1494291..398bb0a69ed 100644
--- a/dlls/user32/tests/msg.c
+++ b/dlls/user32/tests/msg.c
@@ -2666,6 +2666,8 @@ static BOOL can_skip_message(const struct message *expected)
 
     if ((expected->flags & msg_todo) && !strcmp(winetest_platform, "wine")) return TRUE;
 
+    if ((expected->flags & wine_only) && strcmp(winetest_platform, "wine")) return TRUE;
+
     return FALSE;
 }
 
-- 
GitLab

https://gitlab.winehq.org/wine/wine/-/merge_requests/5853