launchpad.net/juju-core/state tests fail

[Michael Hudson-Doyle]

This one seems quite messy:

OOPS: 36 passed, 19 FAILED, 2 FIXTURE-PANICKED, 316 MISSED

I'll attach the output.

[John A Meinel (jameinel)]

There are a few failures here, but all of them talk about:
[LOG] 22.43061 INFO juju.state connection established
export_test.go:104:
    c.Assert(err, gc.IsNil)
... value *errors.errorString = &errors.errorString{s:"cannot create log collection: read tcp 127.0.0.1:49040: i/o timeout"} ("cannot create log collection: read tcp 127.0.0.1:49040: i/o timeout")

All of *those* failures appear in state/open.go
 err := log.Create(&logInfo)
 if err != nil && err.Error() != "collection already exists" {
  return nil, maybeUnauthorized(err, "cannot create log collection")
 }

So it looks like there was some initial failure, which failed to clean up the Mongo database, and then all following tests fail because the db already exists.

Hopefully there's an "easy" fix to clean up a bunch of these.

[Michael Hudson-Doyle (mwhudson)]

I get all manner of failures with the gc toolchain too. So, perhaps, nothing gcc specific here.

[Dave Cheney (dave-cheney)]

Lets remove the "gccgo" tag from this issue.

On Tue, Nov 26, 2013 at 1:32 PM, Michael Hudson-Doyle
<email address hidden> wrote:
> I get all manner of failures with the gc toolchain too. So, perhaps,
> nothing gcc specific here.
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https://bugs.launchpad.net/bugs/1252538
>
> Title:
> launchpad.net/juju-core/state tests fail with gccgo
>
> Status in juju-core:
> Triaged
>
> Bug description:
> This one seems quite messy:
>
> OOPS: 36 passed, 19 FAILED, 2 FIXTURE-PANICKED, 316 MISSED
>
> I'll attach the output.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1252538/+subscriptions

[James Wilson Harshaw IV (jwharshaw)]

Has anyone still been experiencing this bug?

[Dave Cheney (dave-cheney)]

yes

On Sat, Mar 22, 2014 at 12:35 PM, James Wilson Harshaw IV <
<email address hidden>> wrote:

> Has anyone still been experiencing this bug?
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https://bugs.launchpad.net/bugs/1252538
>
> Title:
> launchpad.net/juju-core/state tests fail
>
> Status in juju-core:
> Triaged
>
> Bug description:
> This one seems quite messy:
>
> OOPS: 36 passed, 19 FAILED, 2 FIXTURE-PANICKED, 316 MISSED
>
> I'll attach the output.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1252538/+subscriptions
>