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

2016-05-18 Thread Katherine Cox-Buday

Not sure if this is the isolation problem you're speaking of, but if so, it's 
been fixed.

https://launchpad.net/bugs/1564511

Martin Packman  writes:

> 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 failed due to lack of isolation. Could change
> back to xenial now Curtis added some lxd setup support the the
> makefile I think, but that is unlikely to help speed at all.
>
> Martin

-- 
Katherine

-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev


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

2016-05-17 Thread David Cheney
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)

On Wed, May 18, 2016 at 9:06 AM, Martin Packman
 wrote:
> 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 failed due to lack of isolation. Could change
> back to xenial now Curtis added some lxd setup support the the
> makefile I think, but that is unlikely to help speed at all.
>
> Martin

-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev


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

2016-05-17 Thread Martin Packman
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 failed due to lack of isolation. Could change
back to xenial now Curtis added some lxd setup support the the
makefile I think, but that is unlikely to help speed at all.

Martin

-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev