[
https://issues.apache.org/jira/browse/SUREFIRE-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15537343#comment-15537343
]
Mujtaba Chohan commented on SUREFIRE-1287:
------------------------------------------
Jenkins timeout is set to 200 min. (i.e. abort the build if it's stuck)
> Improve logging to understand why test run failed and report the right failed
> category
> --------------------------------------------------------------------------------------
>
> Key: SUREFIRE-1287
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1287
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.19.1
> Reporter: Samarth Jain
>
> As part of our automated jenkins builds that run after every checkin, we have
> been seeing a lot of these failures:
> Failed to execute goal
> org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:verify
> (ParallelStatsEnabledTest) on project phoenix-core: There was a timeout or
> other error in the fork
> Sample run:
> https://builds.apache.org/job/Phoenix-master/1420/console
> Unfortunately that bit of error information doesn't really help. It would be
> good to know why exactly the fork timed out or failed. What we do know is
> that some of the tests in the Junit category ParallelStatsDisabledTest failed
> to complete. However, failsafe incorrectly reports the failed category as the
> first category that ran. In this case it happened to be
> ParallelStatsEnabledTest. Also to note is the fact that failsafe kicks off
> next category run even before all the tests in the current category have
> finished. I am not sure if that is by design or a bug.
> FYI, [~jamestaylor].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
