[CASSANDRA-14974] Unit test stdout capture is malfunctioning in 4.0

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-alpha1, 4.0
• Component/s: Test/dtest/java, Test/unit
• Severity: Normal
• Assignee: Benedict Elliott Smith
• Reporter: Benedict Elliott Smith

Authors

Benedict Elliott Smith

• Created: 11/Jan/19 12:22
• Updated: 27/Aug/20 15:13
• Resolved: 15/Jan/19 19:14

Description

In 3.x unit tests we make sure to capture stdout to the unit test files, in case tests log to stdout and not to a logger.  However, in 4.0 due to a configuration parameter that is deprecated in logback, the logic is short-circuited silently.

Once fixed, this affects the cleanup of in-jvm dtests which would register an infinite chain of System.out overrides (one for each node), so we make the functionality robust to multiple instantiations, as well as improve its startup/shutdown sequence guarantees.

Issue Links

• relates to: CASSANDRA-14922 In JVM dtests need to clean up after instance shutdown