[
https://issues.apache.org/jira/browse/SUREFIRE-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280352#comment-17280352
]
Alexander Kriegisch edited comment on SUREFIRE-1881 at 2/7/21, 2:17 AM:
------------------------------------------------------------------------
On my machine, if I activate the fork node, there is no {{failsafe-reports}}
directory, just an indefinitely hanging build, I have to kill the process.
Otherwise I would have noticed the dump file. All I see is
{code:none}
[INFO] --- maven-failsafe-plugin:3.0.0-M5:integration-test (integration-test) @
surefire-print-console-problems ---
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
{code}
and then nothing else for minutes.
{quote}What was strange to me was the fact that your code operates with
internal Failsafe code, basically all classes on the JVM.{quote}
Well, that is what Java agents do and what they exist for. But as you can see,
my dummy agent does not modify any byte code, it just prints log lines, so you
can see something and also reproduce the console output garbling effect I see
when the fork node setting is inactive.
was (Author: kriegaex):
On my machine, if I activate the fork node, there is no {{failsafe-reports}}
directory, just an indefinitely hanging build, I have to kill the process.
Otherwise I would have noticed the dump file. All I see is
{code:none}
[INFO] --- maven-failsafe-plugin:3.0.0-M5:integration-test (integration-test) @
surefire-print-console-problems ---
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
{code}
and then nothing else for minutes.
> Java agent printing to native console makes build block when using
> SurefireForkNodeFactory
> ------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-1881
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1881
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
> Affects Versions: 3.0.0-M5
> Reporter: Alexander Kriegisch
> Priority: Major
>
> This is a follow-up to SUREFIRE-1788 which was closed prematurely even though
> there still were open issues which were discussed there initially. Basically
> the situation is as follows:
> * I use Java agents writing to stdOut and stdErr in my tests.
> * I was annoyed that Surefire/Failsafe were writing lots of {{[WARNING]
> Corrupted STDOUT by directly writing to native stream in forked JVM}} lines
> into {{*-jvmRun1.dumpstream}} files. [~tibordigana] then told me to use
> {{<forkNode
> implementation="org.apache.maven.plugin.surefire.extensions.SurefireForkNodeFactory"/>}}
> in my POM in order to fix the issue.
> * I tried this in version 3.0.0-M5, but unfortunately, it makes
> Surefire/Failsafe freeze if a Java agent prints something to stdOut or
> stdErr. This happens both in M5 and in M6-SNAPSHOT after both SUREFIRE-1788
> and SUREFIRE-1809 have been merged in already.
> * My [sample
> project|https://github.com/kriegaex/Maven_Surefire_PrintToConsoleProblems]
> reproduces the issue as soon as you uncomment the option in the POM and run
> {{mvn clean verify}}.
> * The second issue is: *Not* using this option leads to garbled log output
> when a Java agent writes to both stdOut and stdErr before/during tests. See
> comments in class
> [{{Agent.DummyTransformer}}|https://github.com/kriegaex/Maven_Surefire_PrintToConsoleProblems/blob/master/src/main/java/de/scrum_master/dummy/Agent.java]
> for examples for garbled log lines and also comments in
> [pom.xml|https://github.com/kriegaex/Maven_Surefire_PrintToConsoleProblems/blob/master/pom.xml#L36]
> for further information.
> * If the garbled output would also appear with this option activated, cannot
> be tested at present due to the Surefire/Failsafe freeze. I will re-test that
> after the freeze has been fixed and before this issue can be closed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
