State of raring tests

[roger peppe]

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.

do you see this every time? if not, does adding (say)
time.Sleep(3 * time.Second) at the start of testing.MgoDial
make a difference?

presumably you *are* running the right version of mongo
(i think you must be because otherwise it wouldn't have
got as far as TearDownTest).

do you see the error if you run:

go test launchpad.net/cmd/juju -gocheck.vv

on its own. If so, could you pastebin the results of that, please?


On 15 March 2013 05:45, Tim Penhey <tim.penhey at canonical.com> wrote:
> Hi all,
>
> Ian landed today a branch that fixed the git issues with raring that
> some of us saw.
>
> However I still get a bunch of timing related failures (at least I think
> they are timing related).
>
> Here is the pastebin of the failures...
>
> http://paste.ubuntu.com/5615616/
>
> Ideas anyone?
>
> Cheers,
> Tim
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev