From: Adam Dinwoodie <email@example.com> To: Ramsay Jones <firstname.lastname@example.org> Cc: Junio C Hamano <email@example.com>, GIT Mailing-list <firstname.lastname@example.org> Subject: Re: Test failure for v2.16.0-rc0 on cygwin Date: Tue, 2 Jan 2018 11:36:49 +0000 [thread overview] Message-ID: <20180102113649.GC29210@dinwoodie.org> (raw) In-Reply-To: <20171230144019.GB29210@dinwoodie.org> 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. 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. 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, or by opening the UNC path in Explorer and creating the directory there? Adam
next prev parent reply other threads:[~2018-01-02 11:36 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 [this message] 2018-01-02 15:32 ` Ramsay Jones 2018-01-02 19:34 ` Ramsay Jones 2018-01-04 20:55 ` Johannes Schindelin 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=20180102113649.GC29210@dinwoodie.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --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).