From: Junio C Hamano <gitster@pobox.com>
To: Brian Gernhardt <benji@silverinsanity.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Failure in t5516, tests 15 and 16
Date: Tue, 26 Jun 2007 18:44:45 -0700 [thread overview]
Message-ID: <7v4pkuuq5u.fsf@assigned-by-dhcp.pobox.com> (raw)
In-Reply-To: <CFDE3792-403B-4582-B7FB-BC142B79AE63@silverinsanity.com> (Brian Gernhardt's message of "Tue, 26 Jun 2007 21:29:45 -0400")
Brian Gernhardt <benji@silverinsanity.com> writes:
> On Jun 22, 2007, at 10:50 AM, Brian Gernhardt wrote:
>
>> Tests 15 and 16 in script "t5516-fetch-push.sh" fails with "notice:
>> HEAD points to an unborn branch (master)". Is this just bad tests
>> or an actual failure? This is with current master
>> (45fd8bd32dd68ce6b14a406d0abbd6f56490131c) on OS X.
Can you check "cd t && sh -x t5516-fetch-push.sh -i -v"?
I am suspecting that
test "$( cd testrepo && git show-ref | wc -l )" = 1
may have an interesting effect when "wc -l" emits extra
whitespaces. Does this fix it for you?
diff --git a/t/t5516-fetch-push.sh b/t/t5516-fetch-push.sh
index 08d58e1..c0fa2ba 100755
--- a/t/t5516-fetch-push.sh
+++ b/t/t5516-fetch-push.sh
@@ -226,7 +226,7 @@ test_expect_success 'push with colon-less refspec (3)' '
git branch -f frotz master &&
git push testrepo frotz &&
check_push_result $the_commit heads/frotz &&
- test "$( cd testrepo && git show-ref | wc -l )" = 1
+ test 1 = $(cd testrepo && git show-ref | wc -l)
'
test_expect_success 'push with colon-less refspec (4)' '
@@ -239,7 +239,7 @@ test_expect_success 'push with colon-less refspec (4)' '
git tag -f frotz &&
git push testrepo frotz &&
check_push_result $the_commit tags/frotz &&
- test "$( cd testrepo && git show-ref | wc -l )" = 1
+ test 1 = $(cd testrepo && git show-ref | wc -l)
'
next prev parent reply other threads:[~2007-06-27 1:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 14:50 Failure in t5516, tests 15 and 16 Brian Gernhardt
2007-06-27 1:29 ` Brian Gernhardt
2007-06-27 1:44 ` Junio C Hamano [this message]
2007-06-27 1:59 ` Brian Gernhardt
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=7v4pkuuq5u.fsf@assigned-by-dhcp.pobox.com \
--to=gitster@pobox.com \
--cc=benji@silverinsanity.com \
--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