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=5554
Your paranoid android.
=== w2000pro (32 bit filesystem) === filesystem.c:140: Test failed: got 0x800a0046
On 3/10/2014 13:29, 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://newtestbot.winehq.org/JobDetails.pl?Key=5554
Your paranoid android.
=== w2000pro (32 bit filesystem) === filesystem.c:140: Test failed: got 0x800a0046
This is not related to my patch, it doesn't add new tests or change behaviour of existing ones. I think this vm always fails but doesn't submit results so we don't see it on test page.
On Mon, 10 Mar 2014, Nikolay Sivov wrote: [...]
=== w2000pro (32 bit filesystem) === filesystem.c:140: Test failed: got 0x800a0046
This is not related to my patch, it doesn't add new tests or change behaviour of existing ones. I think this vm always fails but doesn't submit results so we don't see it on test page.
It usually sends results but had trouble in the last two runs. Here's its last full report (no scrun failures there): http://test.winehq.org/data/49f3b4282d29890fe3c213d096571af4de2c45cd/index_2...
http://test.winehq.org/data/tests/scrrun:filesystem.html
On 3/10/2014 19:18, Francois Gouget wrote:
On Mon, 10 Mar 2014, Nikolay Sivov wrote: [...]
=== w2000pro (32 bit filesystem) === filesystem.c:140: Test failed: got 0x800a0046
This is not related to my patch, it doesn't add new tests or change behaviour of existing ones. I think this vm always fails but doesn't submit results so we don't see it on test page.
It usually sends results but had trouble in the last two runs. Here's its last full report (no scrun failures there): http://test.winehq.org/data/49f3b4282d29890fe3c213d096571af4de2c45cd/index_2...
I manually tried it today with and without a patch I sent, and without this patch it did fail for me with permissions denied error which is not expect failure reason in this case. It could depend on what current dir is during manual run and automated run. But anyway I want this patch, cause it makes sure that we're using valid temp location.
On Mon, 10 Mar 2014, Nikolay Sivov wrote: [...]
It usually sends results but had trouble in the last two runs. Here's its last full report (no scrun failures there): http://test.winehq.org/data/49f3b4282d29890fe3c213d096571af4de2c45cd/index_2...
I manually tried it today with and without a patch I sent, and without this patch it did fail for me with permissions denied error which is not expect failure reason in this case. It could depend on what current dir is during manual run and automated run. But anyway I want this patch, cause it makes sure that we're using valid temp location.
Sure, I just meant that the VM used to and should be producing test results again.
Your mention of the current directory is interesting as this is the only WineTestBot VM that runs the tests from c:. On that Windows 2000 that's a writable directory though (at least for the administrator).