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] [Commented] (SUREFIRE-1441) Parallel Build Fork Timeout - Impossible To Find Bad Test
Date Fri, 30 Mar 2018 00:34:00 GMT

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

Tibor Digana commented on SUREFIRE-1441:
----------------------------------------

[~m_a]
We cannot talk about multiple modules.
This plugin runs per module and so if you have this error in logs you may already have an
idea how more verbose the output should be. I do not know if ID of forked JVM helps, or a
list of tests as well, but definitely you as a user should specify the ergonomy.

> Parallel Build Fork Timeout - Impossible To Find Bad Test
> ---------------------------------------------------------
>
>                 Key: SUREFIRE-1441
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1441
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Junit 4.7+ (parallel) support, process forking
>    Affects Versions: 2.19.1, 2.20.1
>            Reporter: M A
>            Assignee: Tibor Digana
>            Priority: Major
>
> In any maven project that contains more than a few modules, with a lot of tests, it's
nearly impossible to understand from the build log what test caused a surefire fork timeout
when there's only a message with the following line:
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test
(default-test) on project <XXX>: There was a timeout or other error in the fork ->
[Help 1]
>  
> In my case, we have a Maven project with more than 200 modules, and nearly 20k unit tests.
> Lately we've noticed we don't fail our build upon surefire fork timeout, so we changed
our build behavior (TeamCity in our case) to fail the build in case there was any timeout
for some test.
> But quickly afterwards when the build did start to fail on that issue, we came to understatement
that it's impossible to find this needle in a haystack, and understand what test (not a specific
@Test method, but just the test class name).
> The error message should be more informative and contain useful information for debugging.
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message