Re: go test github.com/juju/juju/state takes > 10 minutes to run

On Tue, May 17, 2016 at 2:14 AM, David Cheney wrote: > My environment has not changed since 14.04, so I'm probably not > running mongo 3.2. > > On Tue, May 17, 2016 at 4:13 PM, Cheryl Jennings > wrote: >> Are you using mongo 3.2? (see

Re: Today I submitted 5 PR's to be merged, 3 failed because mongo shat itself

100x more webscale On Wed, May 18, 2016 at 11:02 AM, Horacio Duran wrote: > For now we are trying to go around mongo issues that make the tests 100x > slower (yes one hundred) once this is fixed we should start using mongo 3.2 > exclusively since 2.4 iirc is EOL or

Re: Today I submitted 5 PR's to be merged, 3 failed because mongo shat itself

For now we are trying to go around mongo issues that make the tests 100x slower (yes one hundred) once this is fixed we should start using mongo 3.2 exclusively since 2.4 iirc is EOL or near. The issue lies in the new storage engine, which we could skip if mmapv1 ( the old one) wasn't also nearing

Re: Today I submitted 5 PR's to be merged, 3 failed because mongo shat itself

What's the plan for mongo 3.2 ? Will we be required to support 2.x versions for the foreseeable future, or is there a possibility to make it a build or run time failure if mongo < 3.2 is installed on the host ? On Wed, May 18, 2016 at 9:01 AM, Martin Packman wrote:

Re: The mean time for a CI run has risen to 33 minutes

The change to Go 1.6 will have increased the _compile_ time for the tests by 3x, but compared to the time of running them, this shouldn't be the main contributor. Go 1.7 will bring significantly improved compile and link times (the linking times are much better than any previous version of Go)

Re: The mean time for a CI run has risen to 33 minutes

On 16/05/2016, David Cheney wrote: > This got significantly worse in the last 6 weeks. What happened ? Either the juju tests are slower, or trusty on aws is slower. It's a fresh cloud instance each run, and still trusty because we switched to xenial and the lxd tests

Today I submitted 5 PR's to be merged, 3 failed because mongo shat itself

What is the story with mongo ? It's constantly causing builds to fail CI because of it's complete shitness. I've heard that some people have moved to mongo 3.2 which fixes the problem, but as CI clearly is running the old rubbish version, this clearly isn't a problem which can be called fixed.

The mean time for a CI run has risen to 33 minutes

This got significantly worse in the last 6 weeks. What happened ? -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: go test github.com/juju/juju/state takes > 10 minutes to run

My environment has not changed since 14.04, so I'm probably not running mongo 3.2. On Tue, May 17, 2016 at 4:13 PM, Cheryl Jennings wrote: > Are you using mongo 3.2? (see bug > https://bugs.launchpad.net/juju-core/+bug/1573294) > > On Mon, May 16, 2016 at 9:52 PM,

Re: go test github.com/juju/juju/state takes > 10 minutes to run

Are you using mongo 3.2? (see bug https://bugs.launchpad.net/juju-core/+bug/1573294) On Mon, May 16, 2016 at 9:52 PM, David Cheney wrote: > Testing this package takes 16 minutes on my machine*; it sure didn't > use to take this long. > > What happened ? > > * yes,