On 4/26/21 7:53 AM, Dmitry Timoshkov wrote:
Marvin testbot@winehq.org wrote:
VM Status Failures Command build success w2008s64 success 0 msxml3_test.exe domdoc w7u_2qxl success 0 msxml3_test.exe domdoc w7u_adm success 0 msxml3_test.exe domdoc w7u_el success 0 msxml3_test.exe domdoc w8 success 0 msxml3_test.exe domdoc w8adm success 0 msxml3_test.exe domdoc w864 success 0 msxml3_test.exe domdoc w1064v1507 success 0 msxml3_test.exe domdoc w1064v1809 success 0 msxml3_test.exe domdoc w1064 success 0 msxml3_test.exe domdoc w10pro64 success 0 msxml3_test.exe domdoc wvistau64 failed 1 msxml3_test64.exe domdoc w2008s64 failed 1 msxml3_test64.exe domdoc w864 failed 1 msxml3_test64.exe domdoc w1064v1507 failed 1 msxml3_test64.exe domdoc w1064v1809 failed 1 msxml3_test64.exe domdoc w1064 failed 1 msxml3_test64.exe domdoc w1064_2qxl failed 1 msxml3_test64.exe domdoc w10pro64 failed 1 msxml3_test64.exe domdoc w10pro64_ar failed 1 msxml3_test64.exe domdoc w10pro64_he failed 1 msxml3_test64.exe domdoc w10pro64_ja failed 1 msxml3_test64.exe domdoc w10pro64_zh_CN failed 1 msxml3_test64.exe domdoc debiant2 success 0 debiant2 failed 1
You can also see the results at: https://testbot.winehq.org/JobDetails.pl?Key=89319
Same patch sent separately runs without failures: https://testbot.winehq.org/JobDetails.pl?Key=89342
The tests crash with STATUS_HEAP_CORRUPTION, which strikes me as something that could cause inconsistent behaviour. Are you sure that you're not introducing a failure here?