maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SUREFIRE-1208) Start stream capture before loading tests
Date Sat, 12 Dec 2015 21:57:46 GMT

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

Tibor Digana updated SUREFIRE-1208:
-----------------------------------
    Description: 
If, when scanClassPath() runs, a class is loaded and that loading process produces a log (via
log4j in our case), the logging framework creates its console appender around the current
stdout stream, before the stream is replaced to start the redirection of stdout and stderr
to a file (when redirectTestOutputToFile is used). The consequences are that stdout gets flooded
with logs (i.e. redirectTestOutputToFile doesn't work).

Scanning the classpath after the capture is started, fixed the issue.

I believe that other providers have the same issue.

> Start stream capture before loading tests
> -----------------------------------------
>
>                 Key: SUREFIRE-1208
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1208
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Junit 4.7+ (parallel) support, Junit 4.x support, TestNG support
>    Affects Versions: 2.19
>            Reporter: Tibor Digana
>            Assignee: Tibor Digana
>             Fix For: 2.19.1
>
>
> If, when scanClassPath() runs, a class is loaded and that loading process produces a
log (via log4j in our case), the logging framework creates its console appender around the
current stdout stream, before the stream is replaced to start the redirection of stdout and
stderr to a file (when redirectTestOutputToFile is used). The consequences are that stdout
gets flooded with logs (i.e. redirectTestOutputToFile doesn't work).
> Scanning the classpath after the capture is started, fixed the issue.
> I believe that other providers have the same issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message