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] [Comment Edited] (SUREFIRE-1287) Improve logging to understand why test run failed and report the right failed category
Date Sun, 02 Oct 2016 19:14:21 GMT

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

Tibor Digana edited comment on SUREFIRE-1287 at 10/2/16 7:14 PM:
-----------------------------------------------------------------

[~jamestaylor]
If you used old config parameter {{forkMode=pertest}}, you would have isolated JVMs per test
class and HBase as well and maybe no issues with database. Not sure if HBase can have datasource
per test. If it can then the solution would be simple, just use {{surefire.forkNumber}} in
datasource definition and {{forkCount=8}} and {{reuseForks=false}}, see the documentation
http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html
It seems to me that the {{surefire.forkNumber}} can be reused because it is thread index in
thread-pool.


was (Author: tibor17):
[~jamestaylor]
If you used old config parameter {{forkMode=pertest}}, you would have isolated JVMs per test
class and HBase as well and maybe no issues with database. Not sure if HBase can have datasource
per test. If it can then the solution could be simple, just use {{surefire.forkNumber}} in
datasource definition and {{forkCount=8}} and {{reuseForks=false}}, see the documentation
http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html
It seems to me that the {{surefire.forkNumber}} can be reused because it is thread index in
thread-pool.

> 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)

Mime
View raw message