From: Junio C Hamano <gitster@pobox.com>
To: Brandon Casey <brandon.casey.ctr@nrlssc.navy.mil>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: t5505-remote.29 not working correctly
Date: Mon, 15 Mar 2010 22:16:06 -0700 [thread overview]
Message-ID: <7v7hpcvobt.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vwrxdueug.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Mon\, 15 Mar 2010 20\:26\:15 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Brandon Casey <brandon.casey.ctr@nrlssc.navy.mil> writes:
>
>> The test titled 'remote prune to cause a dangling symref' is
>> not linked together with &&'s. When the &&'s are added, it
>> does not complete successfully.
>
> Hmm, it looks like f8948e2 (remote prune: warn dangling symrefs,
> 2009-02-08) is internally inconsistent. This is a fix directly on top of
> that commit.
Actually this is a bit deeper than that. We don't get _any_ output to
either standard output nor standard error with the recent code.
If we change the test to:
diff --git a/t/t5505-remote.sh b/t/t5505-remote.sh
index a82c5ff..ca88e29 100755
--- a/t/t5505-remote.sh
+++ b/t/t5505-remote.sh
@@ -507,8 +507,8 @@ test_expect_success 'remote prune to cause a dangling symref' '
(
cd seven &&
git remote prune origin
- ) 2>err &&
- grep "has become dangling" err &&
+ ) >err 2>&1 &&
+ grep "has become dangling" err || exit
: And the dangling symref will not cause other annoying errors
(
so it does not matter whether the output is set to standard output or
standard error, we can bisect this, which points at eafb452 (do_one_ref():
null_sha1 check is not about broken ref, 2009-07-22).
v1.6.3 and onwards seem to be broken.
next prev parent reply other threads:[~2010-03-16 5:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 1:12 t5505-remote.29 not working correctly Brandon Casey
2010-03-16 3:26 ` Junio C Hamano
2010-03-16 5:16 ` Junio C Hamano [this message]
2010-03-16 7:40 ` [PATCH] refs: ref entry with NULL sha1 is can be a dangling symref Junio C Hamano
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=7v7hpcvobt.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=brandon.casey.ctr@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
/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).