flakey store test FAIL: store_test.go:60: StoreSuite.SetUpTest

[John A Meinel]

This test fails as often as it passes for me (about 50/50).

----------------------------------------------------------------------
FAIL: store_test.go:60: StoreSuite.SetUpTest

[LOG] 0:00.001 INFO juju.store store opened, connecting to: localhost:41086
[LOG] 0:00.004 ERROR juju.store error ensuring stat.counters index: E11000 duplicate key error index: juju.stat.tokens.$t_1 dup key: { : "wordpress" }
store_test.go:66:
    c.Assert(err, gc.IsNil)
... value *mgo.LastError = &mgo.LastError{Err:"E11000 duplicate key error index: juju.stat.tokens.$t_1 dup key: { : \"wordpress\" }", Code:11000, N:0, Waited:0, FSyncFiles:0, WTimeout:false, UpdatedExisting:false, UpsertedId:interface {}(nil)} ("E11000 duplicate key error index: juju.stat.tokens.$t_1 dup key: { : \"wordpress\" }")

----------------------------------------------------------------------
PANIC: server_test.go:36: StoreSuite.TestServerCharmInfo

[LOG] 0:00.011 INFO juju.testing reset successfully reset admin password
... Panic: Fixture has panicked (see related PANIC)
OOPS: 24 passed, 8 skipped, 1 FAILED, 6 MISSED
--- FAIL: Test (4.63 seconds)
FAIL
exit status 1
FAIL launchpad.net/juju-core/store 4.703s

I'm running on Trusty with juju-mongodb in case that is relevant (with the fix for bug #1301353).

I have the feeling it is just a race condition where one test is causing an error to occur in Mongo, but it isn't cleaning out the mongo error condition, and then the next test comes along and during SetUp the mongo is still in failure state.

[Andrew Wilkins (axwalk)]

I think I broke this when I changed the store package to use the mgo suite from juju-core/testing.