launchpad-dev team mailing list archive

[Martin Pool <mbp@xxxxxxxxxxxxxx>]

I filed this yesterday: <https://bugs.launchpad.net/launchpad/+bug/891028>

The way getUniqueInteger is implemented using both only per-thread
uniqueness, and also counting on pseudorandom integers to be unique
looks pretty suspicious.

It's interesting that it would now be failing consistently, and only
on ec2.  bac did hit this much earlier this year.

My guess would be that the tests that run prior to this test get the
prng into a state where it will collide, only when run on lucid's
python.