From: Johannes Schindelin <Johannes.Schindelin@gmx.de> To: Ramsay Jones <firstname.lastname@example.org> Cc: Adam Dinwoodie <email@example.com>, Junio C Hamano <firstname.lastname@example.org>, GIT Mailing-list <email@example.com> Subject: Re: Test failure for v2.16.0-rc0 on cygwin Date: Thu, 4 Jan 2018 21:55:10 +0100 (STD) [thread overview] Message-ID: <alpine.DEB.22.214.171.1241042152570.32@MININT-6BKU6QN.europe.corp.microsoft.com> (raw) In-Reply-To: <firstname.lastname@example.org> 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
next prev parent reply other threads:[~2018-01-04 20:55 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-12-30 14:21 Ramsay Jones 2017-12-30 14:40 ` Adam Dinwoodie 2018-01-02 11:36 ` Adam Dinwoodie 2018-01-02 15:32 ` Ramsay Jones 2018-01-02 19:34 ` Ramsay Jones 2018-01-04 20:55 ` Johannes Schindelin [this message] 2018-01-10 23:17 ` Ramsay Jones
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=alpine.DEB.126.96.36.1991042152570.32@MININT-6BKU6QN.europe.corp.microsoft.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Test failure for v2.16.0-rc0 on cygwin' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).