[
https://issues.apache.org/jira/browse/SUREFIRE-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17311059#comment-17311059
]
Alexander Kriegisch edited comment on SUREFIRE-1881 at 3/30/21, 2:18 AM:
-------------------------------------------------------------------------
[~reinhapa], that was a great idea to create GitHub Actions and run the test on
different environments. The information that the problem specifically seems to
affect Windows, is very valuable. I remembered a problem I had with Gradle
which hangs when the Windows mobile hotspot is activated (i.e. if I tether my
local network to other devices via WiFi). So in order to exclude that possible
error source, I first ran the build without mobile hotspot and then with the
WiFi interface completely deactivated (offline build). The problem still occurs.
I even ran the test on Linux - not native but Ubuntu 20.04.1 LTS on Windows
Subsystem for Linux 2. The test hangs on Ubuntu, too. As it did not hang on
your CI build when running in a native environment, probably it is some side
effect of Linux running on a Windows host.
*Update:* I even deactivated the Windows Defender Firewall and Advanced Threat
Protection services by deactivating the firewall for all three zones (local,
domain and public networks). The result is still the same, so it is not a
firewall issue either.
was (Author: kriegaex):
[~reinhapa], that was a great idea to create GitHub Actions and run the test on
different environments. The information that the problem specifically seems to
affect Windows, is very valuable. I remembered a problem I had with Gradle
which hangs when the Windows mobile hotspot is activated (i.e. if I tether my
local network to other devices via WiFi). So in order to exclude that possible
error source, I first ran the build without mobile hotspot and then with the
WiFi interface completely deactivated (offline build). The problem still occurs.
I even ran the test on Linux - not native but Ubuntu 20.04.1 LTS on Windows
Subsystem for Linux 2. The test hangs on Ubuntu, too. As it did not hang on
your CI build when running in a native environment, probably it is some side
effect of Linux running on a Windows host.
> 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
> Assignee: Tibor Digana
> Priority: Major
> Attachments: Bildschirmfoto von 2021-03-29 21-50-25.png,
> image-2021-02-08-12-07-34-183.png, image-2021-03-26-09-48-11-398.png,
> image-2021-03-26-09-52-36-881.png, image-2021-03-26-18-00-37-889.png,
> maven-failsafe-debug-log.txt, screenshot-1.png
>
>
> 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)
