As seen in
http://reports.vapour.ws/releases/issue/57151a54749a562b8595a525
Windows unit tests cannot setup under go 1.6. This issue is likely because unit test were skipping or setting up windows differently based on go version 1.2. This issue is systemic through out all the suite This one example illustrates what breaks hundreds of tests.
c:/users/admini~1/appdata/local/temp/tmpmh6ekt/gogo/src/github.com/juju/juju/juju/testing/conn.go:279:
c.Assert(err, jc.ErrorIsNil)
... value *errors.Err = &errors.Err{message:"Juju cannot bootstrap because no tools are available for your model.\nYou may want to use the 'agent-metadata-url' configuration setting to specify the tools location.\n", cause:error(nil), previous:error(nil), file:"github.com/juju/juju/environs/bootstrap/bootstrap.go", line:161} ("Juju cannot bootstrap because no tools are available for your model.\nYou may want to use the 'agent-metadata-url' configuration setting to specify the tools location.\n")
The errors logs are too large to reliably process. While we can see this issue is in every test run, the outcome analyser frequently cannot identify the issue amongst all the other secondary failures.