All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: fabio.dalfonso@fabiodalfonso.com
Cc: git@vger.kernel.org
Subject: Re: t5539 fails on ubuntu for v2.0.0-rc2
Date: Wed, 07 May 2014 14:45:01 -0700	[thread overview]
Message-ID: <xmqqeh056z6q.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <536A8FF8.7080909@fabiodalfonso.com> (Fabio D'Alfonso's message of "Wed, 07 May 2014 21:56:40 +0200")

Fabio D'Alfonso <fabio.dalfonso@fabiodalfonso.com> writes:

> Hi,
> I am getting this in Ubuntu, something wrong with my env?
> Thanks
>
> root@HDUBVM01:~/builds/git/t# ./t5539-fetch-http-shallow.sh
> ok 1 - setup shallow clone
> not ok 2 - clone http repository
> #
> #        git clone --bare --no-local shallow
> "$HTTPD_DOCUMENT_ROOT_PATH/repo.git" &&
> #        git clone $HTTPD_URL/smart/repo.git clone &&
> #        (
> #        cd clone &&
> #        git fsck &&
> #        git log --format=%s origin/master >actual &&
> #        cat <<EOF >expect &&
> #    7
> #    6
> #    5
> #    4
> #    3
> #    EOF
> #        test_cmp expect actual
> #        )

Does not reproduce for me but I am on Ubuntu 12.04.2 LTS, so...

Running it with the -v option might give you more hints, and
running it as

    $ sh -x ./t5539-fe* -v

might give you more to chew.

I do not think it is wise to run tests as root, though ;-)


> #
> not ok 3 - no shallow lines after receiving ACK ready
> #
> #        (
> #            cd shallow &&
> #            for i in $(test_seq 15)
> #            do
> #                git checkout --orphan unrelated$i &&
> #                test_commit unrelated$i &&
> #                git push -q "$HTTPD_DOCUMENT_ROOT_PATH/repo.git" \
> #                    refs/heads/unrelated$i:refs/heads/unrelated$i &&
> #                git push -q ../clone/.git \
> #                    refs/heads/unrelated$i:refs/heads/unrelated$i ||
> #                exit 1
> #            done &&
> #            git checkout master &&
> #            test_commit new &&
> #            git push  "$HTTPD_DOCUMENT_ROOT_PATH/repo.git" master
> #        ) &&
> #        (
> #            cd clone &&
> #            git checkout --orphan newnew &&
> #            test_commit new-too &&
> #            GIT_TRACE_PACKET="$TRASH_DIRECTORY/trace" git fetch
> --depth=2 &&
> #            grep "fetch-pack< ACK .* ready" ../trace &&
> #            ! grep "fetch-pack> done" ../trace
> #        )
> #
> httpd (pid 10653?) not running
> # failed 2 among 3 test(s)
> 1..3

  reply	other threads:[~2014-05-07 21:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 19:56 t5539 fails on ubuntu for v2.0.0-rc2 Fabio D'Alfonso
2014-05-07 21:45 ` Junio C Hamano [this message]
2014-05-08  4:14   ` Jeff King
2014-05-08  6:02     ` Fabio D'Alfonso
2014-05-08 14:13       ` Fabio D'Alfonso
2014-05-09 15:59       ` Jeff King
2014-05-09 16:43         ` Fabio D'Alfonso
2014-05-09 21:08         ` Junio C Hamano
2014-05-10 14:02           ` Jeff King
2014-05-14 10:14             ` Jeff King
2014-05-14 17:11               ` Junio C Hamano
2014-05-14 19:33                 ` Jeff King
2014-05-08 21:36 ` t5539 fails on ubuntu for v2.0.0-rc2 - the SAME on 12.04 server Fabio D'Alfonso
2014-05-09  8:39   ` t5539 fails on ubuntu for v2.0.0-rc2 - the SAME on 12.04 server - this test was disabled up to 1.9.2 Fabio D'Alfonso
2014-05-09 15:50     ` Jeff King

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=xmqqeh056z6q.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=fabio.dalfonso@fabiodalfonso.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.