All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Keller, Jacob E" <jacob.e.keller@intel.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: t3200-branch.sh number 102 fails when run under make test
Date: Wed, 9 Jul 2014 20:37:51 +0000	[thread overview]
Message-ID: <1404938270.23510.13.camel@jekeller-desk1.amr.corp.intel.com> (raw)

Hello,

I recently cloned the master branch of the git repo, and when I ran make
test, it fails on test 102 of the t3200-branch.sh test cases.

not ok 102 - tracking with unexpected .fetch refspec
#
#               rm -rf a b c d &&
#               git init a &&
#               (
#                       cd a &&
#                       test_commit a
#               ) &&
#               git init b &&
#               (
#                       cd b &&
#                       test_commit b
#               ) &&
#               git init c &&
#               (
#                       cd c &&
#                       test_commit c &&
#                       git remote add a ../a &&
#                       git remote add b ../b &&
#                       git fetch --all
#               ) &&
#               git init d &&
#               (
#                       cd d &&
#                       git remote add c ../c &&
#                       git config remote.c.fetch "+refs/remotes/*:refs/remotes/*" &&
#                       git fetch c &&
#                       git branch --track local/a/master remotes/a/master &&
#                       test "$(git config branch.local/a/master.remote)" = "c" &&
#                       test "$(git config branch.local/a/master.merge)" = "refs/remotes/a/master" &&
#                       git rev-parse --verify a >expect &&
#                       git rev-parse --verify local/a/master >actual &&
#                       test_cmp expect actual
#               )
#
# failed 1 among 102 test(s)
1..102

However, when I run the test file manually it passes. I am currently
running through a verbose output test run to see if I can find more
useful output..

For reference, the commit I am testing against is:

72c779457cd7 ("line-log: use commit_list_append() instead of duplicating its code")

Thanks,
Jake

             reply	other threads:[~2014-07-09 20:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 20:37 Keller, Jacob E [this message]
2014-07-09 20:54 ` t3200-branch.sh number 102 fails when run under make test Jeff King
2014-07-09 21:17   ` Keller, Jacob E
2014-07-09 20:56 ` Keller, Jacob E

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=1404938270.23510.13.camel@jekeller-desk1.amr.corp.intel.com \
    --to=jacob.e.keller@intel.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 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.