The builds for Juju devel and stable were broken by external packages.
http://juju-ci.vapour.ws:8080/job/build-revision/
Fetching http://labix.org/v2/mgo/txn?go-get=1
import "labix.org/v2/mgo/txn": http/https fetch: Get
http://labix.org/v2/mgo/txn?go-get=1: dial tcp 69.163.203.213:80:
connecti
This issue looks real. the 1.18 unittests fail on trusty amd64. I reported
https://bugs.launchpad.net/juju-core/+bug/1318729
-- Forwarded message --
From: CI & CD Jenkins
Date: Mon, May 12, 2014 at 11:47 AM
Subject: [Canonical-juju-qa] Cursed (final): #1354 lp:juju-core/1.18
juju-qa-bot has will be doing mass/automated bug changes for us now.
You can filter those bug emails out since they will be usually be a
case of bugs changing to Fix Committed or Fix Released. I am also
tasking to bot to create the pool of Medium bugs tat we will actively
retriage.
On Fri, May 9,
In the risk of running a bikeshedding paint-fest, I'm curious what the
best-recommended practice is for wrapping function declarations that get a
bit wide.
Currently I'm writing a function that looks like this:
func (c *CustomCaller) MethodCaller(rootName string, version int,
methodName string) (r
I don't want to have this bikeshed - I vote for people to use their
best judgement and permit anything which fits through gofmt.
On Tue, May 13, 2014 at 3:37 PM, John Meinel wrote:
> In the risk of running a bikeshedding paint-fest, I'm curious what the
> best-recommended practice is for wrapping
