testcontainers / testcontainers/testcontainers-java
Disable STDOUT or redirect due to Maven Surefire error
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 1.9k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 9
Description
When running test containers with Maven Surefire I get the following error: https://maven.apache.org/surefire/maven-failsafe-plugin/faq.html#corruptedstream looking in the logs it seems Testcontainers and Surefire are trying to write to stdout at the same time. How can I disable this in Testcontainers?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Maven Surefire FAQ linked in the issue and reproduce the corrupted-stream error while running Testcontainers tests. Trace the competing stdout writes between Testcontainers and Surefire; done means the tests run without the corrupted-stream failure and their output remains usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java
- Domain
- build-system, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100