With the info I now have, I don't think updating the expected sequence is the right approach. Since it only occurs in a full test run on testbot, my options for investigating are limited. We need to either figure out what's weird about the state when newtb-w11pro64-amd-64 runs this test, or isolate it.
From: Esme Povirk esme@codeweavers.com
--- dlls/user32/tests/msg.c | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/dlls/user32/tests/msg.c b/dlls/user32/tests/msg.c index 473b4cfd4a1..8ed608c5d3b 100644 --- a/dlls/user32/tests/msg.c +++ b/dlls/user32/tests/msg.c @@ -2175,11 +2175,7 @@ static const struct message WmTrackPopupMenuMinimizeWindow[] = { { EVENT_OBJECT_LOCATIONCHANGE, winevent_hook|wparam|lparam|winevent_hook_todo, 0, 0 }, { EVENT_OBJECT_LOCATIONCHANGE, winevent_hook|wparam|lparam|optional, 0, 0 }, /* Win7 seems to send this twice. */ { EVENT_SYSTEM_MINIMIZESTART, winevent_hook|wparam|lparam|winevent_hook_todo, 0, 0 }, - { HCBT_ACTIVATE, hook|optional }, /* win11 */ - { WM_NCACTIVATE, sent|optional }, /* win11 */ - { WM_ACTIVATE, sent|optional }, /* win11 */ - { EVENT_SYSTEM_FOREGROUND, winevent_hook|wparam|lparam|optional, 0, 0 }, /* win11 */ - { WM_CANCELMODE, sent|optional }, /* not always sent on win11 */ + { WM_CANCELMODE, sent }, { EVENT_SYSTEM_CAPTUREEND, winevent_hook|wparam|lparam|winevent_hook_todo, 0, 0 }, { WM_CAPTURECHANGED, sent|defwinproc }, { EVENT_SYSTEM_MENUPOPUPEND, winevent_hook|wparam|lparam|winevent_hook_todo, OBJID_CLIENT, 0 },
-
Esme Povirk -
Esme Povirk (＠madewokherd)