Making juju work better with gccgo

[Tim Penhey]

I realise I left this bit hanging:

On 16/05/14 14:41, Tim Penhey wrote:
> A key issue that Dave and I have been poking with a stick is the test
> suite for juju/errgo, as it had some failures with gccgo (all passed
> with gc).

In the end it had to do with the runtime.Caller method for stack
analysis, and the synthetic methods that gccgo was creating.  The
solution was simply enough to convert the tests to use gocheck, that way
the synthetic methods that were being created are higher in the stack
that we ever look in the tests, and it is all good.

Tim