Trivial bugs hurting progress

Curtis Hovey-Canonical curtis at canonical.com
Wed Mar 4 14:54:42 UTC 2015


On Wed, Mar 4, 2015 at 1:05 AM, Andrew Wilkins
<andrew.wilkins at canonical.com> wrote:
> The bot is currently running (I think) Go 1.2. I'm running 1.4, Ian's
> running 1.3, and I'm sure Dave's running tip ;)  Go 1.3+ made map iteration
> less deterministic, so these sorts of bugs are much more likely to occur
> after 1.2. It'd be good to either bump the compiler version to something
> more recent, unless we want to gate things on multiple compilers (maybe gc
> and gccgo, seeing as we currently use both).

While we add our golang archive to all the slaves to ensure golang
1.2.1 is available, apt prefers to use the latest version. On Vivid,
that is golang 1.3, and it very erratic success rate is probably
because of tests aren't ready for a newish golang. Fixing the test
suite will give allow us to make the vivid unit tests voting.

Our test runner script accepts a PPA option. We have added newer
golang and mongos to our experimental PPA, then setup a test to run
with it to prove the Juju was ready for the newer versions. We can do
this again.

-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui



More information about the Juju-dev mailing list