You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/01/13 17:47:01 UTC

[jira] [Commented] (SUREFIRE-1435) Improve Thread Dump. Use prefix "surefire-forkedjvm" in daemon Threads in forked JVM

    [ https://issues.apache.org/jira/browse/SUREFIRE-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16325248#comment-16325248 ] 

Hudson commented on SUREFIRE-1435:
----------------------------------

ABORTED: Integrated in Jenkins build maven-surefire-dev #103 (See [https://builds.apache.org/job/maven-surefire-dev/103/])
[SUREFIRE-1435] Improve Thread Dump. Use prefix "surefire-forkedjvm" in (tibor17: [http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git&a=commit&h=198ef48af094e3de7f132e03da9b70d0da5b246e])
* (edit) surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java


> Improve Thread Dump. Use prefix "surefire-forkedjvm" in daemon Threads in forked JVM
> ------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1435
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1435
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: process forking
>            Reporter: Tibor Digana
>            Assignee: Tibor Digana
>            Priority: Minor
>             Fix For: 2.21.0.Jigsaw
>
>
> Thread Dump contains threads but it is not clear which ones belong to Surefire.
> Use prefix "surefire-forkedjvm" in daemon Threads in forked JVM.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)