On 7/23/20 10:57 AM, 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=75984
Your paranoid android.
=== debiant (32 bit report) ===
kernel32: loader.c:3952: Test failed: ntdll.dll: wrong section 10 loader.c:3952: Test failed: ntdll.dll: wrong section 11 loader.c:3952: Test failed: ntdll.dll: wrong section 12 loader.c:3952: Test failed: ntdll.dll: wrong section 13 loader.c:3952: Test failed: ntdll.dll: wrong section 14 loader.c:3952: Test failed: ntdll.dll: wrong section 15
It seems this happens because ntdll.dll from the build tree changes, but ntdll.dll in system32 doesn't. I'm not sure I have much in the way of ideas to deal with this. Of course the testbot could always update the prefix, but that'd be slow, and I imagine this is an easy pitfall to run into anyway when editing ntdll. I'm not sure if there's any good way to solve this... ideas?