... > I did end up getting some tests running (though I did get a "charm not > found" failure). It did end up getting killed with "test ran to long" after > 10 min. >
For those following along it was cmd/juju DeploySuite.TestUpgradeCharmDir <https://bugs.launchpad.net/juju-core/+bug/1439112> that failed. John =:-> > > So it seems the doc is slightly incomplete, but mostly there. > > John > =:-> > > On Thu, Mar 19, 2015 at 5:40 AM, Gabriel Samfira < > gsamf...@cloudbasesolutions.com> wrote: > >> Hello folks, >> >> It has come to my attention that there may be some confusion in regards >> to some Windows testing. There have been a couple of branches that have >> merged which break windows tests in juju-core. >> >> I would like to remind everyone that there is a guide available at: >> >> http://wiki.cloudbase.it/juju-testing >> >> that will help you set up a testing environment on Windows. Also, if >> there are any questions regarding Windows weirdness, please feel free to >> contact me on irc (gsamfira) or bogdanteleaga. We will be more then >> happy to help you navigate any Windows issues you might have. >> >> >> Kind regards, >> Gabriel >> -- >> Juju-dev mailing list >> Juju-dev@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju-dev >> > >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
