[PATCH STABLE] test: display used python hash seed

Brendan Cully brendan at kublai.com
Wed Jan 30 11:37:13 CST 2013


On Wednesday, 30 January 2013 at 16:34, Pierre-Yves David wrote:
> On Wed, Jan 30, 2013 at 10:25:39AM -0500, Augie Fackler wrote:
> > On Wed, Jan 30, 2013 at 01:32:28AM +0100, Pierre-Yves David wrote:
> > > # HG changeset patch
> > > # User Pierre-Yves David <pierre-yves.david at ens-lyon.org>
> > > # Date 1359505444 -3600
> > > # Branch stable
> > > # Node ID 7918b4ffff358db8c27131a55696dbdb4a2c0296
> > > # Parent  68eecbaf1bd32a616748331cc9f22d55b1316ce3
> > > test: display used python hash seed
> > >
> > > We keep using a random seed for each run, but we "compute" it ourself to be able
> > > to reproduce a failed test run.
> > 
> > LGTM, though I'm not sure I'd throw this on stable. Hold onto it and
> > resend after the first?
> 
> This may helps to understand some of the buildbot error. I recommend using it ASAP.

I will implement the same logic in buildbot today, so there's no real rush.


More information about the Mercurial-devel mailing list