Turning on gating for Windows tests before all tests were passing is premature and is now blocking us from landing critical fixes for beta12 that we need to release this week for inclusion into xenial. With the race tests, we got all of those passing before turning on gating. We need to do the same for the Windows tests. We need to deactivate gating on Windows at this stage. Of course we need to fix the tests, but turning on gating before that is done is counterproductive given what we need to get done this week.
On 08/07/16 03:26, Aaron Bentley wrote: > Hi Juju developers, > > As requested by juju-core, we have added --race and Windows unit tests > to gated landings. These tests are run concurrently, not sequentially, > but all must complete before code can be landed. > > As a practical matter, this means that landings are now impossible until > the Windows and --race tests can pass. > > The output from this initial version is a bit crude-- it will tell you > which tasks failed (e.g. "windows"), and you then need to look at the > corresponding logs under the Jenkins artifacts. We aim to improve this > soon. > > Aaron > > > -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
