Marvin testbot@winehq.org wrote:
=== w1064v1809 (32 bit report) ===
user32: win.c:4013: Test failed: message 0738 available
=== w1064_tsign (32 bit report) ===
user32: win.c:4073: Test failed: hwnd 00020178/00020178 message 0200 win.c:4077: Test failed: hwnd 00020178/00020178 message 0201 win.c:4086: Test failed: hwnd 0011005A/0011005A message 0202 win.c:4089: Test failed: hwnd 0011005A/0011005A message 0201
=== w10pro64 (32 bit report) ===
user32: win.c:2271: Test failed: style 0x200000: expected !100 win.c:2271: Test failed: style 0x300000: expected !100
=== w10pro64 (64 bit report) ===
user32: win.c:2271: Test failed: style 0x200000: expected !100 win.c:2271: Test failed: style 0x300000: expected !100
=== w10pro64_zh_CN (64 bit report) ===
user32: win.c:10245: Test failed: pos = 00fa00fa win.c:10249: Test failed: pos = 00fa00fa win.c:10253: Test failed: pos = 00fa00fa
=== debiant2 (64 bit WoW report) ===
user32: menu.c:2337: Test failed: test 25
These failures don't seem to be related to the patch.