git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: <git@vger.kernel.org>
Subject: [Test Failure] t5570 - not cloned
Date: Fri, 1 May 2015 11:04:48 -0400	[thread overview]
Message-ID: <003901d08420$2b9fd7a0$82df86e0$@nexbridge.com> (raw)

Greetings - and asking for a bit of help resolving test failures.

I'm having an issue with t5570 at 2.3.7 which seems to be a regression from
2.3.3 (currently installed), but I cannot be sure. This test failed prior to
2.3.0 in the box, worked from 2.3.0 to 2.3.3 - suggesting that it may be
environmental, not actually in git. Making some assumptions, it looks like
the URL for the test repository is not correct and may depend on localhost
resolving properly - which DNS does not do well on this box (outside my
control, we are multi-home, and localhost does not resolve to 127.0.0.1 or
[::1]). Only t5570 #'s 3-5 fail and I found a strange message in the output
of the test seemingly referring to a bad repo name. I would really
appreciate some pointers on where to look next and how to go about resolving
this. I am happy to try to work through this on 2.4.0 if that would be more
efficient for the team. Anything relating to git-daemon makes me nervous in
terms of installing the code.

Platform is HP NonStop (Posix-esque environment):

In the test output:
*** t5570-git-daemon.sh ***
<snip>
not ok 3 - clone git repository
#
#               git clone "$GIT_DAEMON_URL/repo.git" clone &&
#               test_cmp file clone/file
#
not ok 4 - fetch changes via git protocol
#
#               echo content >>file &&
#               git commit -a -m two &&
#               git push public &&
#               (cd clone && git pull) &&
#               test_cmp file clone/file
#
not ok 5 - remote detects correct HEAD
#
#               git push public master:other &&
#               (cd clone &&
#                git remote set-head -d origin &&
#                git remote set-head -a origin &&

And

../git/t/trash directory.t5570-git-daemon: cat output
fatal: remote error: repository not exported: /repo.git

Additional context: t0025, t0301, t3900, t9001, t9020 are not 100% but the
issues are acceptable - we can discuss separately.

Cheers,
Randall

-- Brief whoami: NonStop&UNIX developer since approximately
UNIX(421664400)/NonStop(211288444200000000)
-- In my real life, I talk too much.

             reply	other threads:[~2015-05-01 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01 15:04 Randall S. Becker [this message]
2015-05-02 18:24 ` [Test Failure] t5570 - not cloned Randall S. Becker

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='003901d08420$2b9fd7a0$82df86e0$@nexbridge.com' \
    --to=rsbecker@nexbridge.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;
as well as URLs for NNTP newsgroup(s).