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

Attempt 1: make sure to always flush buffered logs #409

Merged
merged 1 commit into from
Aug 31, 2021

Conversation

olafurpg
Copy link
Member

Previously, buffered logs would sometimes not get flushed resulting in
lost test report output. See #408. This commit adds an extra attempt to
flush the buffered logs inside the sbt testing framework in case the
logs don't get flushed by the JUnit test listener. I'm not 100% sure
this fixes the problem but it seems worth a short and it shouldn't cause
a regression.

Previously, buffered logs would sometimes not get flushed resulting in
lost test report output. See scalameta#408. This commit adds an extra attempt to
flush the buffered logs inside the sbt testing framework in case the
logs don't get flushed by the JUnit test listener. I'm not 100% sure
this fixes the problem but it seems worth a short and it shouldn't cause
a regression.
@olafurpg olafurpg merged commit 92f3ad9 into scalameta:main Aug 31, 2021
@olafurpg olafurpg deleted the flush-buffers branch August 31, 2021 07:51
@olafurpg
Copy link
Member Author

cc/ @jenshalm

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

Successfully merging this pull request may close these issues.

1 participant