unit tests with mongo3.2 fail with timeouts

[Christopher Lee]

With the unit tests being run with mongo3.2 the tests can take between 10x and 100x longer to run resulting in timeout failures.

As seen: http://reports.vapour.ws/releases/issue/562a396a749a561a0619d324

[Andrew Wilkins (axwalk)]

https://github.com/juju/juju/pull/7297

[Andrew Wilkins (axwalk)]

Still being seen in CI: http://reports.vapour.ws/releases/5198/job/run-unit-tests-xenial-amd64/attempt/132#highlight

[John A Meinel (jameinel)]

That particular test seems to be stuck in a TearDownTest. I wonder if there
was just a hang trying to cleanup:

sync.runtime_SemacquireMutex(0xc4203a0cf4)
 /usr/lib/go-1.8/src/runtime/sema.go:62 +0x34
sync.(*Mutex).Lock(0xc4203a0cf0)
 /usr/lib/go-1.8/src/sync/mutex.go:87 +0x9d
gopkg.in/mgo%2ev2.(*mongoSocket).SimpleQuery(0xc42027c9a0,
0xc42027d180, 0x5, 0x17835cd, 0x5, 0xc4203a0ce0, 0xa)
 /home/ubuntu/juju-core_2.2-beta4/src/gopkg.in/mgo.v2/socket.go:367 +0x28b
gopkg.in/mgo%2ev2.(*Database).run(0xc420ef7858, 0xc42027c9a0,
0x153e980, 0xc4207106c0, 0x0, 0x0, 0xc4207106c0, 0xc420ef7770)
 /home/ubuntu/juju-core_2.2-beta4/src/gopkg.in/mgo.v2/session.go:3261 +0x1b3
gopkg.in/mgo%2ev2.(*Database).Run(0xc420ef7858, 0x153e980,
0xc4207106c0, 0x0, 0x0, 0x0, 0x0)
 /home/ubuntu/juju-core_2.2-beta4/src/gopkg.in/mgo.v2/session.go:656 +0xcd
gopkg.in/mgo%2ev2.(*Database).DropDatabase(0xc420ef7858, 0x17bf707, 0x27)
 /home/ubuntu/juju-core_2.2-beta4/src/gopkg.in/mgo.v2/session.go:2624 +0x132
github.com/juju/testing.(*MgoInstance).Reset(0x21dd6e0, 0x0, 0x0)
 /home/ubuntu/juju-core_2.2-beta4/src/github.com/juju/testing/mgo.go:738 +0x26c
github.com/juju/juju/provider/dummy.(*environState).destroyLocked(0xc420252820)
 /home/ubuntu/juju-core_2.2-beta4/src/github.com/juju/juju/provider/dummy/environs.go:380
+0x12f
github.com/juju/juju/provider/dummy.(*environState).destroy(0xc420252820)
 /home/ubuntu/juju-core_2.2-beta4/src/github.com/juju/juju/provider/dummy/environs.go:339
+0x75
github.com/juju/juju/provider/dummy.Reset(0xc4209e24b0)
 /home/ubuntu/juju-core_2.2-beta4/src/github.com/juju/juju/provider/dummy/environs.go:318
+0x1d9
github.com/juju/juju/juju/testing.(*JujuConnSuite).tearDownConn(0xc42014dc00,
0xc4209e24b0)
 /home/ubuntu/juju-core_2.2-beta4/src/github.com/juju/juju/juju/testing/conn.go:650
+0x142
github.com/juju/juju/juju/testing.(*JujuConnSuite).TearDownTest(0xc42014dc00,
0xc4209e24b0)
 /home/ubuntu/juju-core_2.2-beta4/src/github.com/juju/juju/juju/testing/conn.go:135
+0x39

On Mon, May 8, 2017 at 6:30 AM, Andrew Wilkins <<email address hidden>
> wrote:

> Still being seen in CI: http://reports.vapour.ws/releases/5198/job/run-
> unit-tests-xenial-amd64/attempt/132#highlight
>
> ** Changed in: juju
> Status: Fix Committed => Triaged
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1686920
>
> Title:
> unit tests with mongo3.2 fail with timeouts
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1686920/+subscriptions
>

[Anastasia (anastasia-macmood)]

This is a very old report. It references code that is no longer there. In addition, we have not seen this failure for years.

I am closing this report so any re-occurrences need to be treated as a new bug and deserve separate report.