Hi,
While running your changed tests on Windows, 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=31999
Your paranoid android.
=== w7u (32 bit msi) === The task timed out
On 07/03/2017 12:50 AM, Marvin wrote:
Hi,
While running your changed tests on Windows, 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=31999
Your paranoid android.
=== w7u (32 bit msi) === The task timed out
I'm not entirely sure what's up with this. I noticed that the testbot consistently timed out on xp/2003/vista(/2008?) with my patches starting with 358ed0d8. They only take a few seconds to run on my Windows 7 machine—which to be sure does have much better hardware than a VM would, but I can't be sure what part of my patches in particular is slowing down or hanging the machine.
Can anyone perhaps try running the package tests on their own machine and see if they get any distinct slowness? Thanks.
On Mon, 2017-07-03 at 08:22 -0500, Zebediah Figura wrote:
=== w7u (32 bit msi) === The task timed out
I'm not entirely sure what's up with this. I noticed that the testbot consistently timed out on xp/2003/vista(/2008?) with my patches starting with 358ed0d8. They only take a few seconds to run on my Windows 7 machine—which to be sure does have much better hardware than a VM would, but I can't be sure what part of my patches in particular is slowing down or hanging the machine.
Can anyone perhaps try running the package tests on their own machine and see if they get any distinct slowness? Thanks.
The sequence that causes the hang is closehandle_sequence. Changing externalui_message_callback to not touch the record handle if the message is INSTALLMESSAGE_TERMINATE makes the hang go away.