Hello Francois,
I've been looking at these test failures a bit (which are not related to the patches I sent).
The errors correspond to the situation as if PROC_THREAD_ATTRIBUTE_PARENT_PROCESS process attribute is silently ignored. Which results in both unwanted process creation success (which should fail due to invalid parent process handle) and the attribute not working and thus failing the test responsible for checking the actual parent itself. I could not find any specific privilege responsible for this attribute. Since the error happens on these two machines only (and only on 32 bit), maybe there are some specifics common and unique to these machines which can give a clue why that is not working?
Regards, Paul.
On 5/13/21 15:22, 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=90359
Your paranoid android.
=== w1064 (32 bit report) ===
kernel32: process.c:4171: Test failed: Got unexpected ret 0x1, GetLastError() 1813. process.c:4185: Test failed: Got unexpected ret 0x1, GetLastError19(8c): p181r3o.ce process.c:4114: Test failed: Got unexpected ret 0, level 2, GetLastError() 6. process.c:4121: Test failed: Got parent id 7400, parent_data.parent_id 0. process.c:4265: Test failed: Unexpected return value, error 203.
=== w1064_tsign (32 bit report) ===
kernel32: process.c:4171: Test failed: Got unexpected ret 0x1, GetLastError() 1813. process.c:4185: Test failed: Got unexpected ret 0x1, GetLastError() 1813. process.c:4114: Test failed: Got unexpected ret 0, level 2, GetLastError() 6. process.c:4121: Test failed: Got parent id 6764, parent_data.parent_id 0.