On 02/01/18 11:36, Adam Dinwoodie wrote:
> On Saturday 30 December 2017 at 02:40 pm +0000, Adam Dinwoodie wrote:
>> On Saturday 30 December 2017 at 02:21 pm +0000, Ramsay Jones wrote:
>>> Hi Junio, Adam,
>>>
>>> Just a quick note about the failure of the test-suite on cygwin.
>>> In particular, test t5580-clone-push-unc.sh #3, like so:
>>>
>>> <snip>
>>>
>>> Adam, are you running the tests on Windows 10?
>>
>> I'm only routinely testing on Windows 10 x86_64, but between holidays
>> various, I've not had the tests running for the past couple of weeks.
>> I'm kicking off a build now in the name of verifying I see the same
>> problem.
>
> I'm not able to reproduce this: t5580 is passing on both my Windows 10
> test systems on v2.16.0-rc0.
Hmm, interesting. BTW, I should have noted which version I'm on (just
in case it matters): Windows 10 Home, Version 1709, OS Build 16299.125.
I am reasonably up-to-date on cygwin:
$ uname -a
CYGWIN_NT-10.0 satellite 2.9.0(0.318/5/3) 2017-09-12 10:18 x86_64 Cygwin
$
[I only recently updated to the creator's update (I'm not signed up to
the 'insider program'), and so could not try out WSL until now. I would
not recommend it to anyone who wants to develop software - a Linux VM
is an _order of magnitude_ faster, so ... ]
> Looking at your output, it sounds like there's something slightly odd
> with your directory permissions. I agree the mixed slashes look odd,
> but given the test is passing on both my systems, I don't think that can
> be the problem.
The directory permissions look fine to me (except for //localhost/C$).
> I suspect you're going to need to do some more digging yourself given
> this appears to be a permissions issue on your system. For a start,
> when you get to the failing `mkdir` with a UNC path, are you able to
> create the equivalent directory using Cygwin's `mkdir` but specifying a
> regular non-UNC path,
yes, this is not a problem.
or by opening the UNC path in Explorer and
> creating the directory there?
I didn't get to this because ...
I just tried running the test again by hand, and I can't get it to fail!
Hmm, I have just set off a complete test-suite run, so I won't be able
to report on that for a while ... ;-)
I have an idea: when running the failing tests the other day, I was
remotely logged in via ssh (I have cygwin sshd running on my win10
box), but today I was logged in directly. The sshd daemon is run by
a privileged user, so maybe that could be related ... dunno.
I will have to investigate some more. (If you have any ideas ... :-D )
ATB,
Ramsay Jones
