Hi, On Tue, 2 Jan 2018, Ramsay Jones wrote: > On 02/01/18 15:32, Ramsay Jones wrote: > > 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: > [snip] > >> I'm not able to reproduce this: t5580 is passing on both my Windows 10 > >> test systems on v2.16.0-rc0. > [snip] > > 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 ... ;-) > > Yep, as expected, the test-suite passes no problem now! ;-) > > > 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. > > Also, when logged-in remotely it fails consistently, when logged-in > directly it passes consistently. :-D You are most likely hitting cmd.exe at some point there. In cmd.exe, there are some restrictions that are inherited by spawned processes AFAIU. For example, the current directory cannot be a UNC path. You are most likely running the interactive Cygwin session in MinTTY? Then you do not get those restrictions. If you start Cygwin in a cmd.exe window, you should see the exact same test failures again. Ciao, Dscho
