On 1/6/21 3:55 PM, 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=83809
Your paranoid android.
=== w10pro64 (testbot log) ===
An error occurred while waiting for the test to complete: the 1052 process does not exist or is not a child process
=== w10pro64 (testbot log) ===
An error occurred while waiting for the test to complete: the 880 process does not exist or is not a child process
=== w10pro64_ar (testbot log) ===
An error occurred while waiting for the test to complete: the 7716 process does not exist or is not a child process
=== w10pro64_he (testbot log) ===
An error occurred while waiting for the test to complete: the 7752 process does not exist or is not a child process
=== w10pro64_ja (testbot log) ===
An error occurred while waiting for the test to complete: the 7996 process does not exist or is not a child process
=== w10pro64_zh_CN (testbot log) ===
An error occurred while waiting for the test to complete: the 7900 process does not exist or is not a child process
I think w10pro64 has some issues, or something is already wrong with this specific test on this specific windows version. For instance, the same test with a no-op patch gives the same kind of failures here:
https://testbot.winehq.org/JobDetails.pl?Key=83808#k305