Potential fix for sporadic issues with AsterixClusterLifeCycleIT.tearDown()
I think there was a race between these two adjacent methods in tearDown(), the latter of which looks like it isn't
even doing what I intended it to do at the moment. I haven't been able to observe this sporadic failure after changing
it so the latter one goes after the printing of the output of the former, which blocks and therefore would stop any
issues of this type.
Change-Id: I57ac2117c42a0b798f3249846f0b49927c64d870
Reviewed-on: http://fulliautomatix.ics.uci.edu:8443/91
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: Chris Hillery <ceej@lambda.nu>
1 file changed