Comment 4 for bug 1271745

Sorry, no, that won't persist a bootstrap between runs, but it will stop break the test run if a test fails.

As for the don't tear down and bootstrap over and over again, there's a few different models for this and people from both camps asking. One is where a bootstrap is provided once and every test uses that. The other is like the first, only the test runner force destroys all machines in the deployment after each test (saving time for each bootstrap). I'm uncertain how requiring postmortem inspection of a failed test is not satisfied by --set-e and how having a common bootstrap addresses that