[tor-dev] Tor project automation work

Nicolas Vigier boklm at mars-attacks.org
Tue Dec 10 17:07:38 UTC 2013

On Tue, 10 Dec 2013, Lunar wrote:

> Nicolas Vigier:
> > Ok, we can have a test rebuilding several times the files that are most
> > likely to become non deterministic. However it would be better if we can
> > find some way to trigger those non-deterministic builds with only two
> > builds. Maybe we can try something like this :
> > 
> > - a library that we put in LD_PRELOAD as a wrapper on readdir to return
> >   directory entries in random order instead of inodes number, so it's
> >   more likely to be different on each build.
> > 
> > - a python library that we put in PYTHONPATH, to override dict.iterkeys
> >   to return keys in random order. If I understand ticket #10159
> >   correctly, it was caused by iterkeys returning keys in the same order
> >   most of the time, but not all the times.
> I would suggest using reverse order instead of random order. Random
> order has the probability of being just like the original order.

Indeed, reverse order is better.

> For readdir(3), have a look at:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719845#39

This looks like exactly what we need. Thanks !

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20131210/21a4beb9/attachment.sig>

More information about the tor-dev mailing list