All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>
Subject: Bug: t5813 failing on Cygwin
Date: Sat, 07 Nov 2015 12:11:29 +0000	[thread overview]
Message-ID: <563DEA71.1080808@dinwoodie.org> (raw)

In the process of pulling up the Cygwin Git release from v2.5.3, I've 
discovered t5813 is failing, and appears to have been failing since it 
was first introduced in a5adace.

I've not yet done any significant digging into the problem myself; I'm 
reporting here now in case in the hope someone else will have a better 
idea what's going on.

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.

Adam

             reply	other threads:[~2015-11-07 12:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-07 12:11 Adam Dinwoodie [this message]
2015-11-07 18:45 ` Bug: t5813 failing on Cygwin Jeff King
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=563DEA71.1080808@dinwoodie.org \
    --to=adam@dinwoodie.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.