You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2019/01/11 12:23:00 UTC

[jira] [Created] (CASSANDRA-14974) Unit test stdout capture is malfunctioning in 4.0

Benedict created CASSANDRA-14974:
------------------------------------

             Summary: Unit test stdout capture is malfunctioning in 4.0
                 Key: CASSANDRA-14974
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14974
             Project: Cassandra
          Issue Type: Bug
          Components: Test/dtest, Test/unit
            Reporter: Benedict
            Assignee: Benedict
             Fix For: 4.0


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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org