On 2020-07-06 11:52, Zhiyi Zhang wrote:
On 7/6/20 5:07 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=74847
Your paranoid android.
=== debiant (32 bit report) ===
dxgi: dxgi: Timeout
=== debiant (32 bit French report) ===
dxgi: dxgi: Timeout
=== debiant (build log) ===
0024:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 0024:err:winediag:nodrv_CreateWindow The explorer process failed to start. Task: WineTest did not produce the win32_ja_JP report
=== debiant (32 bit WoW report) ===
dxgi: dxgi: Timeout
=== debiant (64 bit WoW report) ===
dxgi: dxgi: Timeout
No sure what's wrong yet. But an empty test also triggers such errors. See https://testbot.winehq.org/JobDetails.pl?Key=74856#k101 And the errors seem to be a regression. I will take a look.
I tracked down some timeout issues with the user32 monitor test here:
https://www.winehq.org/pipermail/wine-devel/2020-July/169357.html
I believe the dxgi test also alter display modes so could it be the same thing?