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://newtestbot.winehq.org/JobDetails.pl?Key=3099
Your paranoid android.
=== w864 (32 bit filtergraph) === filtergraph: unhandled exception c0000005 at 00404347
=== w864 (64 bit filtergraph) === filtergraph: unhandled exception c0000005 at 0000000000403DF2
Hi.
No, it's not new. This runs has it already http://test.winehq.org/data/ddd6fd1ecbc4c25cf6c69202934c8bf2a3f01daf/index_W...
On Tue, Oct 29, 2013 at 6:38 PM, Marvin testbot@winehq.org 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://newtestbot.winehq.org/JobDetails.pl?Key=3099
Your paranoid android.
=== w864 (32 bit filtergraph) === filtergraph: unhandled exception c0000005 at 00404347
=== w864 (64 bit filtergraph) === filtergraph: unhandled exception c0000005 at 0000000000403DF2
On Tue, 29 Oct 2013, Nikolay Sivov wrote:
Hi.
No, it's not new. This runs has it already http://test.winehq.org/data/ddd6fd1ecbc4c25cf6c69202934c8bf2a3f01daf/index_W...
Yep. It would actually be nice to fix it since it's one of the failures that happens systematically accross the board on Windows 8 and 8.1, including on real hardware:
http://test.winehq.org/data/cb0ef08839e515d7a9053923d27ef8899978a263/index_W...