Trunk broken at revision 821

[David Cheney]

My apologies. I have chased this to a breakage in golang tip. 


On Friday, 11 January 2013 at 12:48 PM, David Cheney wrote:

> Hi Folks,
> 
> I just did a fresh checkout of juju-core trunk and on my machine it is very broken. I'm going to boot up a clean ec2 instance and verify there, I cannot believe that trunk would be this broken without someone else noticing.
> 
> lucky(~/src/launchpad.net/juju-core (http://launchpad.net/juju-core)) % go test ./... 2>/dev/null | egrep '^FAIL.+laun'
> FAIL launchpad.net/juju-core/charm (http://launchpad.net/juju-core/charm) 0.417s
> FAIL launchpad.net/juju-core/cmd/juju (http://launchpad.net/juju-core/cmd/juju) 41.999s
> FAIL launchpad.net/juju-core/state (http://launchpad.net/juju-core/state) 29.707s
> FAIL launchpad.net/juju-core/worker/uniter (http://launchpad.net/juju-core/worker/uniter) 79.324s
> FAIL launchpad.net/juju-core/worker/uniter/charm (http://launchpad.net/juju-core/worker/uniter/charm) 1.988s
> 
> 
> Can anyone else confirm the breakage ?
> 
> Cheers
> 
> Dave 
> 
> 
> 
> -- 
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com (mailto:Juju-dev at lists.ubuntu.com)
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev