On Wed, May 11, 2022 at 01:53:07PM -0500, Marvin wrote:
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=114467
Your paranoid android.
=== w864 (64 bit report) ===
oleacc: main.c:1920: Test failed: hwnd != 0xdeadf00d!
=== w1064v1507 (64 bit report) ===
oleacc: main.c:1920: Test failed: hwnd != 0xdeadf00d!
=== w1064v1809 (64 bit report) ===
oleacc: main.c:1920: Test failed: hwnd != 0xdeadf00d!
=== w1064 (64 bit report) ===
oleacc: main.c:1920: Test failed: hwnd != 0xdeadf00d!
=== w1064_2qxl (64 bit report) ===
oleacc: main.c:1920: Test failed: hwnd != 0xdeadf00d!
=== w1064_adm (64 bit report) ===
oleacc: main.c:1920: Test failed: hwnd != 0xdeadf00d!
=== w1064_tsign (64 bit report) ===
oleacc: main.c:1920: Test failed: hwnd != 0xdeadf00d!
=== w10pro64 (64 bit report) ===
oleacc: main.c:1920: Test failed: hwnd != 0xdeadf00d!
=== w10pro64_en_AE_u8 (64 bit report) ===
oleacc: main.c:1920: Test failed: hwnd != 0xdeadf00d!
=== w10pro64_ar (64 bit report) ===
oleacc: main.c:1920: Test failed: hwnd != 0xdeadf00d!
=== w10pro64_ja (64 bit report) ===
oleacc: main.c:1920: Test failed: hwnd != 0xdeadf00d!
=== w10pro64_zh_CN (64 bit report) ===
oleacc: main.c:1920: Test failed: hwnd != 0xdeadf00d!
Oof, guess I should've run the 64-bit tests on the testbot before sending this. This patch could also probably be split into two. I'll fix these issues and then resend.