On 10/04/18 20:49, 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=37602
Your paranoid android.
=== wvistau64 (64 bit ndr_marshall) === TestBot process died unexpectedly
=== wvistau64 (64 bit server) === 0608:server: unhandled exception c0000005 at 000007FEFEE110EF 0930:server: unhandled exception c0000005 at 000007FEFEE110EF 0250:server: unhandled exception c0000005 at 000007FEFEE110EF server.c:1781: Test failed: WaitForSingleObject
=== w7pro64 (64 bit server) === 0ad4:server: unhandled exception c0000005 at 000007FEFD76F0FF 0af8:server: unhandled exception c0000005 at 000007FEFD76F0FF 0b20:server: unhandled exception c0000005 at 000007FEFD76F0FF server.c:1781: Test failed: WaitForSingleObject The previous 4 run(s) terminated abnormally
=== w864 (64 bit server) === 074c:server: unhandled exception c0000005 at 00007FFB253D6836 07c8:server: unhandled exception c0000005 at 00007FFB253D6836 0d0c:server: unhandled exception c0000005 at 00007FFB253D6836 server.c:1781: Test failed: WaitForSingleObject
=== w1064 (64 bit server) === 0f28:server: unhandled exception c0000005 at 00007FFC3B7B0140 0118:server: unhandled exception c0000005 at 00007FFC3B7B0140 0f3c:server: unhandled exception c0000005 at 00007FFC3B7B0140 server.c:1781: Test failed: WaitForSingleObject
A successful test using recompiled widl from patch 1/4 is here: