State of raring tests

[Julian Edwards]

On Monday 18 Mar 2013 15:10:30 Tim Penhey wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 16/03/13 02:26, John Arbash Meinel wrote:
> > On 2013-03-15 14:51, roger peppe wrote:
> >> looks like something to do with mongo or ssl.
> >> 
> >> i'm surprised you think it's timing-related - it looks like it's
> >> in a non-racy part of the code to me, but perhaps there's some
> >> odd interaction with mongod starting up.
> > 
> > Actually, if you think about it, I'm curious where he got mongod
> > for Raring. The archive Julian put together only had Quantal, and
> > the pre-built binaries on s3 I thought only had Precise and
> > Quantal. (It is possible that they are static enough to work on
> > Raring, but maybe only enough to start up but not to tear down?)
> 
> OK...
> 
> I had got Julian to rebuild his packages for raring, and they can be
> found here:
> 
> https://launchpad.net/~julian-edwards/+archive/mongodb
> 
> These are based on 2.2.3 that is now in the distro, but with SSL
> compiled in (AFAIK).
> 
> These builds cause the tests to panic and flail their arms about.
> 
> I grabbed the binaries from
> https://s3.amazonaws.com/juju-dist/tools/mongo-2.2.0-quantal-amd64.tgz
> and put these in the path, and then the tests pass.
> 
> I'm not sure what the difference is between the binaries in the 2.2.0
> build, and the ones that are build in Julian's package, but the tests
> don't like it.
> 
> Tim
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> 
> iEYEARECAAYFAlFGd4oACgkQd1fvI4G7WRDwTgCfSr0YDXnCTxFQR0ek/hrX1pCp
> SB4An3ScQyyOyiqHqg7cz83NdRQbb9oD
> =f0yh
> -----END PGP SIGNATURE-----

It could be a problem in 2.2.3 I guess.  I used the same compile options as I 
did for 2.2.2 so I'm not sure what's up.  At least, Tim confirms that libssl 
is linked to the executable produced by the build.