I noticed recently that when you use the
--parallel flag with
swift test, depending on the environment, specifically on some CI providers, you can end up with some pretty gnarly output:
Testing: 0%  0%  0%  0%  1%  1%  1%  1%  2%  2%  ...
I was hoping to be able to work around this by redirect stdout, or stderr, but then if you have test failures, both this progress output and the failures go to the same stream.
It seems like there are a few possible ways to fix this:
- Change progress and test failure output to go to different streams
- Introduce some sort of
--quietflag you can pass to
swift testthat would exclude this progress output, and for non-parallel tests, probably exclude everything but failures (like xcpretty)
- Try to fix the parallel test output logic to handle whatever configurations we're hitting here
I'd be happy to take a stab at the implementation but I wanted to gauge what people thought would be the right solution before working on it. Thoughts?