-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to hide output from successful test binaries. #5089
Comments
Libtest in rust-lang/rust is what's printing most of this, so maybe this would be best reported there? |
I disagree (although there might also be improvements that could be made there). I think that we want to hide the output regardless of the source. The libtest output is just an example of a general problem. |
As there hasn't been any activity here in over 6 months I've marked this as stale and if no further activity happens for 7 days I will close it. I'm a bot so this may be in error! If this issue should remain open, could someone (the author, a team member, or any interested party) please comment to that effect? The team would be especially grateful if such a comment included details such as:
Thank you for contributing! If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable! |
This is still relevant because it is still making it awkward to manage projects with a lot of test binaries. |
Right now passing tests in a harness have no output shown which is nice for seeing the output of those that have failed. However if you have tests in multiple targets (for example in
lib/
,tests/
bin/
...) the output quickly gets to be quite noisy.Some of these binaries have no tests and a couple of them only have a single test case. However they print at least 6 lines each. Pushing the warning off the top of my screen.
It would be great if there was an option to hide successful test harness output by default. This would probably require a "all good" message at the end to confirm the everything is complete but would nicely keep errors near the bottom and noise low.
The text was updated successfully, but these errors were encountered: