TestSuppressOutput is a flake

[carolynvs]

I have noticed that TestSuppressOutput (and only that test) sometimes fails because not all of the bundle output is captured, often it stops at "installing bundle" or whatever and then the rest isn't in the captured string. So when the test checks for a substring in the output, it isn't found and it fails.

I can't tell if this is a really subtle bug in porter that only reproduces in this one test (not likely?) or if we have a problem with our test helpers perhaps?

It's flaking out often enough that it's interfering with releases so if anyone has ideas on how to either restructure the test, the test bundle or insights on where this bug could be, I need help. 😀