From: Jeff King <peff@peff.net>
To: Adam Dinwoodie <adam@dinwoodie.org>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: Bug: t5813 failing on Cygwin
Date: Sat, 7 Nov 2015 13:45:27 -0500 [thread overview]
Message-ID: <20151107184527.GA4483@sigill.intra.peff.net> (raw)
In-Reply-To: <563DEA71.1080808@dinwoodie.org>
On Sat, Nov 07, 2015 at 12:11:29PM +0000, Adam Dinwoodie wrote:
> Specifically, I'm seeing t5813 subtests 9-13 and 15-19 failing. This happens
> with a clean build straight from the Git source tree (git clean -dfx && make
> configure && ./configure && make && cd t && ./t5813-proto-disable-ssh.sh) as
> well as builds using the Cygwin packaging paraphernalia.
What does the output of "./t5813-proto-disable-ssh.sh -v -i" show?
It seems strange that it would fail only on Cygwin; this code doesn't
really use any platform-dependent features. It's also weird that it
fails _only_ for ssh, and _only_ on the tests that are using "ssh://"
URLs are not "host:path" syntax.
I tried building on Linux with the Cygwin build knobs found in
config.mak.uname, but I couldn't get it to fail. I also wondered if the
test was doing something with the shell that might not be portable, but
I don't see anything interesting.
-Peff
next prev parent reply other threads:[~2015-11-07 18:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 12:11 Bug: t5813 failing on Cygwin Adam Dinwoodie
2015-11-07 18:45 ` Jeff King [this message]
2015-11-07 19:20 ` Adam Dinwoodie
2015-11-07 21:02 ` Dennis Kaarsemaker
2015-11-07 21:21 ` Ramsay Jones
2015-11-07 23:05 ` Ramsay Jones
2015-11-07 23:32 ` Dennis Kaarsemaker
2015-11-08 1:46 ` Ramsay Jones
2015-11-08 7:11 ` Torsten Bögershausen
2015-11-07 23:24 ` Adam Dinwoodie
2015-11-08 5:10 ` Jeff King
2015-11-08 9:54 ` [PATCH] t5813: avoid creating urls that break on cygwin Dennis Kaarsemaker
2015-11-09 15:45 ` Jeff King
2015-11-09 17:49 ` Dennis Kaarsemaker
2015-11-09 17:50 ` Jeff King
2015-11-08 13:21 ` Bug: t5813 failing on Cygwin 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151107184527.GA4483@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=adam@dinwoodie.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 NNTP newsgroup(s).