git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Brian Gernhardt <benji@silverinsanity.com>
Cc: "git@vger.kernel.org List" <git@vger.kernel.org>
Subject: Re: Intermittent Failures in t1450-fsck (Bisected)
Date: Thu, 5 May 2011 17:17:36 -0400	[thread overview]
Message-ID: <20110505211736.GA7256@sigill.intra.peff.net> (raw)
In-Reply-To: <1A288BE9-F001-4CAD-8A89-4B4D6F0F246B@silverinsanity.com>

On Thu, May 05, 2011 at 05:07:54PM -0400, Brian Gernhardt wrote:

> On May 5, 2011, at 4:04 PM, Brian Gernhardt wrote:
> 
> > On May 5, 2011, at 5:32 AM, Jeff King wrote:
> > 
> >> Given that the problem seems racy and intermittent, have you tried
> >> running under valgrind?
> > 
> > This is on my OS X laptop and last I knew valgrind was very buggy on OS X, so I've never tried it.  I'll install it now and see if I can get anything useful out of it.
> 
> I will note the test _reliably_ fails when run in parallel with other tests.

It might be interference from another test, though in general they
should all be in their own little sandboxes. It could just be a race
condition that gets triggered more reliably when the system is under
load.

> Under valgrind I get the following error.  I will note that attempting
> to run the full test suite with valgrind gives lots of similar errors
> in many tests.  (All conditional jump in deflate, allocated in
> write_loose_object.)

This is probably a false positive. On Linux we see these in libz because
it has some weird optimized loop that can read past the end of the
buffer (though I have usually see it in the inflate code path, not
deflate).

-Peff

      reply	other threads:[~2011-05-05 21:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 17:11 Intermittent Failures in t1450-fsck Brian Gernhardt
2011-05-05  6:46 ` Intermittent Failures in t1450-fsck (Bisected) Brian Gernhardt
2011-05-05  9:32   ` Jeff King
2011-05-05 20:04     ` Brian Gernhardt
2011-05-05 21:03       ` Jeff King
2011-05-05 21:58         ` Brian Gernhardt
2011-05-07 20:25           ` Brian Gernhardt
2011-05-11 11:43             ` Jeff King
2011-05-05 21:07       ` Brian Gernhardt
2011-05-05 21:17         ` Jeff King [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=20110505211736.GA7256@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=benji@silverinsanity.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).