Comment 6 for bug 1394223

I looked at the failure from:
http://10.125.0.203:8080/job/RunUnittests-s390x/277/console

Which appears to have the fix that was landed for:
https://bugs.launchpad.net/juju/+bug/1754021

namely, we wait for 'hackyGoroutineDone' before we check m4.InstanceStatus which should mean that we won't tear down the connection for m3 until that goroutine is done.
However, a panic() could be obscuring the original error. Imagine that checkStartInstance failed with an error, which would then raise an exception, which would the never call close(thatsAllFolks) and never waits for hackyGoroutineDone.