git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: carbonated beverage <ramune@net-ronin.org>
To: Eric Wong <normalperson@yhbt.net>
Cc: Christian Couder <chriscool@tuxfamily.org>,
	git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: t9106 failure, bisect weirdness
Date: Wed, 21 Nov 2007 01:57:27 -0800	[thread overview]
Message-ID: <20071121095727.GA13211@net-ronin.org> (raw)
In-Reply-To: <20071121091001.GA23266@soma>

> I can't reproduce it at all on any of my boxes, but does the following
> one-liner fix it consistently?

FYI, it's a Core 2 Duo @ 2GHz (Thinkpad Z61t).

Yup, I ran the test in a loop, and it went through 15 iterations without
failure.  This patch works for me.

Thanks!

-- DN
Daniel

      reply	other threads:[~2007-11-21  9:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 23:06 t9106 failure, bisect weirdness carbonated beverage
2007-11-20  4:52 ` Christian Couder
2007-11-20  6:13   ` carbonated beverage
2007-11-21  4:08     ` Christian Couder
2007-11-21  4:56       ` carbonated beverage
2007-11-21  9:10         ` Eric Wong
2007-11-21  9:57           ` carbonated beverage [this message]

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=20071121095727.GA13211@net-ronin.org \
    --to=ramune@net-ronin.org \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=normalperson@yhbt.net \
    /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).