[ https://issues.apache.org/jira/browse/SUREFIRE-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15537586#comment-15537586 ]
Tibor Digana commented on SUREFIRE-1287: ---------------------------------------- Can you fix it so that HBase wold be started in pre-integration-tests phase via a script? What about kill it after the tests. {code} String name = ManagementFactory.getRuntimeMXBean().getName(); int indexOfAt = name.indexOf( '@' ); if ( indexOfAt > 0 ) { String pid = name.substring( 0, indexOfAt ); getLog().warn( "Going to kill process with PID " + pid ); List<String> args = new ArrayList<String>(); if ( System.getProperty( "os.name" ).startsWith( "Windows" ) ) { args.add( "taskkill" ); args.add( "/PID" ); } else { args.add( "kill" ); args.add( "-INT" ); } args.add( pid ); try { new ProcessBuilder( args ).start(); } catch ( IOException e ) { getLog().error( "Unable to spawn process. Killing with System.exit.", e ); } } else { getLog().warn( "Unable to determine my PID... Using System.exit" ); } {code} > 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)