[
https://issues.apache.org/jira/browse/SUREFIRE-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17149892#comment-17149892
]
Alexander Kriegisch edited comment on SUREFIRE-1788 at 7/2/20, 5:46 AM:
------------------------------------------------------------------------
>From May until around middle of June I checked Maven Central almost every day,
>then I stopped looking, so I did not notice the release on June 17th. I have
>just upgraded and am experiencing what I described in my previous message and
>nobody was interested in: My builds freeze.
*Update:*
* One module freezes, but only with {{<forkNode
implementation="org.apache.maven.plugin.surefire.extensions.SurefireForkNodeFactory"/>}}.
Without that option, the module runs the integration tests but also fails with
M5, with M4 it works.
* Another module always fails on M5, with or without that option. On M4 it
also works.
There could be some connection to me using Java agents for byte code
instrumentation in my integration tests in the second module, but in the first
module I don't use any agents. As soon as I switch back to M4, my tests all run
fine again. There seems to be something wrong in Surefire. I cannot use the new
release like this.
was (Author: kriegaex):
>From May until around middle of June I checked Maven Central almost every day,
>then I stopped looking, so I did not notice the release on June 17th. I have
>just upgraded and am experiencing what I described in my previous message and
>nobody was interested in: My builds freeze.
*Update:*
* One module freezes, but only with {{<forkNode
implementation="org.apache.maven.plugin.surefire.extensions.SurefireForkNodeFactory"/>}}.
Without that option, the module runs the integration tests but also fails with
M5, with M4 it works.
* Another module always fails on M5, with or without that option. On M4 is
also works.
There could be some connection to me using Java agents for byte code
instrumentation in my integration tests in the second module, but in the first
module I don't use any agents. As soon as I switch back to M4, my tests all run
fine again. There seems to be something wrong in Surefire. I cannot use the new
release like this.
> Unhandled native logs in SurefireForkChannel
> --------------------------------------------
>
> Key: SUREFIRE-1788
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1788
> Project: Maven Surefire
> Issue Type: Task
> Components: Maven Failsafe Plugin, Maven Surefire Plugin, process
> forking
> Reporter: Tibor Digana
> Assignee: Tibor Digana
> Priority: Major
> Fix For: 3.0.0-M5
>
>
> This is related only to the internal change of the version 3.0.0-M5 itself.
> The
> [stdOut|https://github.com/apache/maven-surefire/blob/master/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/extensions/SurefireForkChannel.java#L153]
> should be printed to INFO on the console.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
