Oct. 25, 2022
10:01 a.m.
On Tue Oct 25 09:55:09 2022 +0000, **** wrote: > Marvin replied on the mailing list: > ``` > Hi, > It looks like your patch introduced the new failures shown below. > Please investigate and fix them before resubmitting your patch. > If they are not new, fixing them anyway would help a lot. Otherwise > please ask for the known failures list to be updated. > The tests also ran into some preexisting test failures. If you know how > to fix them that would be helpful. See the TestBot job for the details: > The full results can be found at: > https://testbot.winehq.org/JobDetails.pl?Key=125391 > Your paranoid android. > === w7u_2qxl (32 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w7u_adm (32 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w7u_el (32 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w8 (32 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w8adm (32 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w864 (32 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w1064v1507 (32 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w1064v1809 (32 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w1064 (32 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w1064_tsign (32 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w10pro64 (32 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w864 (64 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w1064v1507 (64 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w1064v1809 (64 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w1064 (64 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w1064_2qxl (64 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w1064_adm (64 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w1064_tsign (64 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w10pro64 (64 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w10pro64_en_AE_u8 (64 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w10pro64_ar (64 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w10pro64_ja (64 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === w10pro64_zh_CN (64 bit report) === > ntdll: > file.c:4036: Test failed: got 0xc000000d > === debian11 (32 bit report) === > d3d9: > device.c:6067: Test failed: Failed to create a D3D object. > ``` 1. I'm not freeing the memory properly in the test 2. I'm not passing in the correct buffer sizwe and 3. Wine just ignores the pased-in size -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1148#note_12013