Given how often people still use "--upload-tools" for things like private
clouds (and is definitely the one used for local provider), I'd really
worry about having a jujud on your local machine that wasn't built with the
same toolchain as the one you get from "juju bootstrap" in other cases.
Very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2015-11-30 10:36 AM, John Meinel wrote:
> Given how often people still use "--upload-tools" for things like
> private clouds (and is definitely the one used for local provider),
> I'd really worry about having a jujud on your local machine that
On Mon, Nov 30, 2015 at 10:36 AM, John Meinel wrote:
> Given how often people still use "--upload-tools" for things like private
> clouds (and is definitely the one used for local provider), I'd really worry
> about having a jujud on your local machine that wasn't built
As of this morning, the unit tests pass on xenial (thanks to Andrew
for getting them over the hump) using Go 1.5
On Tue, Dec 1, 2015 at 3:21 AM, Curtis Hovey-Canonical
wrote:
> On Mon, Nov 30, 2015 at 10:36 AM, John Meinel wrote:
>> Given how often
Good discussion. I have one nuance that I think we want to discuss in
SFO. Namely, controlling the Juju tool chain.
Juju QA uses CI to make many of the things we releases, such as win
agents. We use Launchpad/Ubuntu to make Ubuntu agents and clients.
Juju QA qill soon have access to ARM hardware.
On 27/11/15 08:43, Michael Hudson-Doyle wrote:
> On 27 November 2015 at 02:24, Martin Packman
> wrote:
>> On 26/11/2015, Andrew Wilkins wrote:
>>> Hi (mostly Curtis),
>>>
>>> Is there a plan to bump the minimum Go version? Some of our
Martin: Can you setup a unit test job that uses Go 1.5 ? I will apply
the same process I did for the -race job, to get the build voting,
then reenable the tests that were skipped.
On Fri, Nov 27, 2015 at 12:24 AM, Martin Packman
wrote:
> On 26/11/2015, Andrew
On 26/11/2015, David Cheney wrote:
> Martin: Can you setup a unit test job that uses Go 1.5 ? I will apply
> the same process I did for the -race job, to get the build voting,
> then reenable the tests that were skipped.
We've had that since near the start of the wily
On 27 November 2015 at 09:39, Tim Penhey wrote:
> On 27/11/15 08:43, Michael Hudson-Doyle wrote:
>> On 27 November 2015 at 02:24, Martin Packman
>> wrote:
>>> On 26/11/2015, Andrew Wilkins wrote:
Hi
On Fri, Nov 27, 2015 at 7:49 AM Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
> On 27 November 2015 at 09:39, Tim Penhey wrote:
> > On 27/11/15 08:43, Michael Hudson-Doyle wrote:
> >> On 27 November 2015 at 02:24, Martin Packman
> >>
Hi (mostly Curtis),
Is there a plan to bump the minimum Go version? Some of our dependencies do
not build with Go 1.2. The LXD provider only builds with Go 1.3 (I think?),
and I've got a PR up that updates the azure-sdk-for-go dependency, but it's
blocked because the newer doesn't build with Go
11 matches
Mail list logo