Skip to content
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

disable noise when printing test results #2414

Open
svalaskevicius opened this issue Aug 29, 2024 · 4 comments
Open

disable noise when printing test results #2414

svalaskevicius opened this issue Aug 29, 2024 · 4 comments

Comments

@svalaskevicius
Copy link

svalaskevicius commented Aug 29, 2024

I spent a while to figure out how to disable noisy specs2 results duplication only to find that it's done by bloop: https://github.com/scalacenter/bloop/blob/34840d485a56abc9d388796392df46151b3ac93b/frontend/src/main/scala/bloop/testing/LoggingEventHandler.scala#L103C16-L135

is there a way to get rid of it (an option or smthg)?

(specifically the "Failed: ... " part)

Thanks!

@svalaskevicius
Copy link
Author

to explain, the result like from the below is already better:

bloop test ... | awk '/===============================================/{h=!h} {if (!h) print $0}' 

@tgodzik
Copy link
Contributor

tgodzik commented Aug 30, 2024

Thanks for reporting! Could post how it looks for you right now and how you would want it to look like?

I am not sure I will have time to work on it, but it is worth to put as much information as possible. Besides that we are always open to a contribution.

@svalaskevicius
Copy link
Author

hi, right now, it prints all specs2 output, and then repeatedly prints errors and failures, but the bloop failure printing is inferior as it omits the line numbers.

when there is more than a few errors, I have to always scroll past the bloop failure printout, to find what specs2 reported it - to find the line numbers..

I don't think bloop's failure reprinting adds much value, and it could simply be removed - the test frameworks print their outputs - don't they all? essentially that's what the hacky awk snippet is doing there

@tgodzik
Copy link
Contributor

tgodzik commented Sep 2, 2024

you might be right here, I think we can remove it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants