geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kirk Lund (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (GEODE-6159) SystemOutRule does not play well with Log4j in tests that verify logging behavior
Date Fri, 11 Oct 2019 22:05:00 GMT

     [ https://issues.apache.org/jira/browse/GEODE-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kirk Lund resolved GEODE-6159.
------------------------------
    Resolution: Won't Fix

> SystemOutRule does not play well with Log4j in tests that verify logging behavior
> ---------------------------------------------------------------------------------
>
>                 Key: GEODE-6159
>                 URL: https://issues.apache.org/jira/browse/GEODE-6159
>             Project: Geode
>          Issue Type: Bug
>          Components: logging, tests
>            Reporter: Kirk Lund
>            Assignee: Kirk Lund
>            Priority: Major
>
> We need to find a better solution that is simpler than having to specify a custom log4j2.xml
with LoggerContextRule but works better than SystemOutRule.
> The problem with using SystemOutRule to test output from a logger is that log4j captures
System.out into its own static final reference. So tests like this must be run in their own
forked JVM.
> See GEODE-6158 for some background about the tests that do specify custom log4j2.xml
config files.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message