On Tue, Oct 14, 2014 at 10:23 PM, Tim Penhey <tim.pen...@canonical.com> wrote:
> Hi folks,
>
> while testing today I noticed that debug-log is broken for the local
> provider because the all-machines.log file isn't being written out.
>
> Not done any more follow up yet.
I don't understand this sentence.
We can see from a recent failure in CI that all-machines.log was
written out and captured:
http://juju-ci.vapour.ws:8080/job/local-deploy-utopic-amd64/500/
I ran 1.21-alpha2-trusty-amd64 and debug-log and it worked for me.
Which version of juju did you test? Shouldn't there be a bug tracking
this issue?
--
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
