Re: valgrind patches, was Re: What's cooking in git.git (Jan 2009, #04; Mon, 19)
- From
Jeff King <peff@peff.net>
- Date
- Jan 21, 2009, 00:15 UTC
- Message-ID
- <20090121001551.GB18169@coredump.intra.peff.net>
- In-Reply-To
- <alpine.DEB.1.00.0901210105470.19014@racer>
On Wed, Jan 21, 2009 at 01:10:22AM +0100, Johannes Schindelin wrote:
> > Hmm. I suppose that would work, since every test run is trying to create > > the same state. > > Yep, that's what I meant with "no race".
Right, but it is still possible to screw it up, if your creation process does a delete-create. But it looks like you did it correctly in your patch (try to create, and if you fail because it's there, assume it's right).
> Heh. Okay. I was convinced that your valgrind patch predated my -j<n> > patch...
I think I did an early version that did predate it, but then another round afterwards.
> In any case, I already found a bug in the nth_last series, thanks to your > work, which I'll send in a minute.
Yay! It's nice when infrastructure work like this actually pays off.
Thanks for picking up this topic...I can drop the size of my ever-growing git todo list by one. :)
-Peff