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
Assertion calls on CapturedOutput with Kotlin are very slow #32033
Comments
Could you please attach a sample project that we can download and run. The snippets are helpful, but a full project with a build file will be better to ensure we're on the same versions and haven't made a mistake copying the code. |
Also, if you can replicate this in Java that will be even better as there's one less moving part. |
example-capturedoutput-32033.zip Example project attached. It's related to the root log level. When I set it to INFO, it works. When it's set as DEBUG, the test hangs. |
I can't reproduce the hanging test with the provided sample, but the The problem is specific to Kotlin. A statement like When calling Marking this for team attention so we can decide what, if anything, we want to do about this. |
Thank you @scottfrederick! I appreciate you investigating. |
I think we should add some caching to |
CapturedOutput
contains a string causes test to hang
I have a test that checks to see if a string is in the captured output. I expect this to work because
CapturedOutput
implementsCharSequence
. However, the test hangs indefinitely.I would expect that this works the same as if I had called
output.all
.ApplicationTest.kt
Application.kt
The text was updated successfully, but these errors were encountered: