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=83637
Your paranoid android.
=== w2008s64 (32 bit report) ===
comctl32: listview: Timeout
=== w7u_2qxl (32 bit report) ===
comctl32: listview: Timeout
=== w7u_adm (32 bit report) ===
comctl32: listview: Timeout
=== w7u_el (32 bit report) ===
comctl32: listview: Timeout
=== w8 (testbot log) ===
The task timed out
=== w8adm (testbot log) ===
The task timed out
=== w864 (32 bit report) ===
comctl32: listview: Timeout
=== w1064v1507 (32 bit report) ===
comctl32: listview: Timeout
=== w1064v1809 (32 bit report) ===
comctl32: listview: Timeout
=== w1064 (32 bit report) ===
comctl32: listview: Timeout
=== w10pro64 (32 bit report) ===
comctl32: listview: Timeout
=== wvistau64 (64 bit report) ===
comctl32: listview: Timeout
=== w2008s64 (64 bit report) ===
comctl32: listview: Timeout
=== w864 (64 bit report) ===
comctl32: listview: Timeout
=== w1064v1507 (64 bit report) ===
comctl32: listview: Timeout
=== w1064v1809 (64 bit report) ===
comctl32: listview: Timeout
=== w1064 (64 bit report) ===
comctl32: listview: Timeout
=== w1064_2qxl (64 bit report) ===
comctl32: listview: Timeout
=== w10pro64 (64 bit report) ===
comctl32: listview: Timeout
=== w10pro64_ar (64 bit report) ===
comctl32: listview: Timeout
=== w10pro64_he (64 bit report) ===
comctl32: listview: Timeout
=== w10pro64_ja (64 bit report) ===
comctl32: listview: Timeout
=== w10pro64_zh_CN (64 bit report) ===
comctl32: listview: Timeout
The patch can't work due to infinite loops, but with that fixed it gives me failures on Windows, and no failures on Wine. So I'm not sure what it's supposed to demonstrate.