Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-14974

Unit test stdout capture is malfunctioning in 4.0

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Fix Version/s: 4.0
    • Component/s: Test/dtest, Test/unit
    • Labels:
      None
    • Severity:
      Normal

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                benedict Benedict
                Reporter:
                benedict Benedict
                Authors:
                Benedict
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: