Junio C Hamano <gitster@xxxxxxxxx> writes: > Brandon Casey <brandon.casey.ctr@xxxxxxxxxxxxxxx> 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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html