Open Aviss opened 5 years ago
I'm having the same problem. Did you find a workaround?
Unfortunately not. We eventually switched back to regular Arquillian and running integration tests with a managed Wildfly container
Damn. Ok, thanks for the info.
Issue Overview
Trying to use the log-strategy succedes in finding the right log entries but runs into an exception regardless
Expected Behaviour
The container is considered started when the correct log entires are found
Current Behaviour
As soon as the log entries are found, an exception is thrown (stacktrace below)
Steps To Reproduce
Additional Information
Debugging this issue I found that
LogScanningAwaitStrategy#await
is about to return when the exception is thrown. The exception is coming from closing theLogContainerResultCallback
opened as a try-with-resource.I'm using:
Stacktrace:
docker-compose.yml
Dockerfile