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=14265
Your paranoid android.
=== w8 (32 bit console) === console.c:1489: Test failed: [13] Expected output count to be 0, got 2359244 console.c:1489: Test failed: [15] Expected output count to be 0, got 2359244 console.c:1489: Test failed: [18] Expected output count to be 3735928559, got 2359244 console.c:1733: Test failed: [13] Expected output count to be 0, got 2359244 console.c:1733: Test failed: [15] Expected output count to be 0, got 2359244 console.c:1733: Test failed: [18] Expected output count to be 3735928559, got 2359244
On Sun, 14 Jun 2015 06:57:33 -0500, 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=14265
Your paranoid android.
=== w8 (32 bit console) === console.c:1489: Test failed: [13] Expected output count to be 0, got 2359244 console.c:1489: Test failed: [15] Expected output count to be 0, got 2359244 console.c:1489: Test failed: [18] Expected output count to be 3735928559, got 2359244 console.c:1733: Test failed: [13] Expected output count to be 0, got 2359244 console.c:1733: Test failed: [15] Expected output count to be 0, got 2359244 console.c:1733: Test failed: [18] Expected output count to be 3735928559, got 2359244
These errors are unrelated to the patch.