ppc64le timeouts cursing things
Tim Penhey
tim.penhey at canonical.com
Fri Jul 17 03:59:38 UTC 2015
Hi Curtis,
I have been looking at some of the recent cursings from ppc64le, and the
last two included timeouts for the worker/uniter tests.
On my machine, amd64, i7, 16 gig ram, I get the following:
$ time go test
2015-07-17 03:53:03 WARNING juju.worker.uniter upgrade123.go:26 no
uniter state file found for unit unit-mysql-0, skipping uniter upgrade step
OK: 51 passed
PASS
ok github.com/juju/juju/worker/uniter 433.256s
real 7m24.270s
user 3m18.647s
sys 1m2.472s
Now lets ignore the the logging output that someone should fix, we can
see how long it takes here. Given that gccgo on power is slower, we are
going to do two things:
1) increase the timeouts for the uniter
2) change the uniter tests
WRT to point 2, most of the uniter tests are actually fully functional
end to end tests, and should not be run every time we land code.
They should be moved into the featuretest package.
Thanks,
Tim
More information about the Juju-dev
mailing list