From: David Turner <dturner@twopensource.com>
To: "Øyvind A. Holm" <sunny@sunbase.org>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: t5150-request-pull.sh fails on newest master in Debian
Date: Fri, 04 Jul 2014 13:22:50 -0700 [thread overview]
Message-ID: <1404505370.3109.15.camel@stross> (raw)
In-Reply-To: <CAA787r=78UWio3E==s+J2PbVqshQdWXpS9hiJrmNz+F0vLiuGg@mail.gmail.com>
On Thu, 2014-07-03 at 23:55 +0200, Øyvind A. Holm wrote:
> When compiling newest master (v2.0.1-472-g6f92e5f) on Debian 7.5
> (64-bit), t5150-request-pull.sh fails when compiling with
>
> $ make configure
> $ ./configure --prefix=/usr/local/varprg/git.master.v2.0.1-472-g6f92e5f
> $ make prefix=/usr/local/varprg/git.master.v2.0.1-472-g6f92e5f
> $ make
> $ cd t
> $ ./t5150-request-pull.sh
Are you sure you're not running under valgrind? I can reproduce the test
failures when I run under valgrind because I didn't add the right stuff
to the suppression files (patch to follow).
I also just went ahead and got a Linode running Debian 7.5 (64-bit), and
I still can't reproduce the problem. Do you have any additional
reproduction info that I need here?
next prev parent reply other threads:[~2014-07-04 20:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 21:55 t5150-request-pull.sh fails on newest master in Debian Øyvind A. Holm
2014-07-03 22:16 ` David Turner
[not found] ` <CAA787rmroFsjk9=ar0e_4o3hUpfDBi+9J4nrNyHHMZq-5q4skw@mail.gmail.com>
2014-07-03 23:02 ` Øyvind A. Holm
2014-07-03 22:19 ` Øyvind A. Holm
2014-07-04 20:22 ` David Turner [this message]
2014-07-05 0:09 ` Øyvind A. Holm
2014-07-05 1:58 ` David Turner
2014-07-05 14:24 ` Øyvind A. Holm
2014-07-05 19:00 ` [PATCH] refs.c: handle REFNAME_REFSPEC_PATTERN at end of page David Turner
[not found] ` <xmqq7g3pdoy7.fsf@gitster.dls.corp.google.com>
2014-07-09 11:48 ` Øyvind A. Holm
2014-07-09 0:52 ` t5150-request-pull.sh fails on newest master in Debian Øyvind A. Holm
2014-07-09 1:18 ` David Turner
2014-07-09 11:44 ` Øyvind A. Holm
2014-07-09 14:52 ` René Scharfe
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=1404505370.3109.15.camel@stross \
--to=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=sunny@sunbase.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.