Hi folks,
When I'm about to propose or land something, I'll typically run make
check, or just go test ./... to ensure I haven't broken some far-away
package. This can be quite slow, unnecessarily so if the packages changed
don't feature in the dependencies of some of our longer running tests.
I
I propose we make a small sample program that exercises error returns in
several typical ways, including the non-trivial scenarios, and then make
one implementation for each competing error package, so we can see how they
work out in real code.
The code can be very terse, since there's no need
Hi Sebastian,
I believe Marco is looking into this.
In the meantime, a workaround that works for me is to set the dataset-size
to a fixed (low) value, e.g.:
juju deploy mysql
juju set mysql dataset-size='512M'
Cheers,
Daniele
On Mon, Feb 10, 2014 at 3:03 PM, Sebastian sebas5...@gmail.com
