I set up a freestyle project to build by invoking maven out of a shell script. My guess is that will show the timed out tests as happens when run locally in a terminal. See http://54.241.6.143/job/HBase-0.94-Freestyle
On Mon, Apr 8, 2013 at 5:45 PM, Andrew Purtell <[email protected]> wrote: > See for example http://54.241.6.143/job/HBase-0.94/71/console: > > [...] > [JENKINS] Recording test results > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 1:18:06.862s > [INFO] Finished at: Mon Apr 08 08:10:20 UTC 2013 > [INFO] Final Memory: 32M/501M > [INFO] > ------------------------------------------------------------------------ > [JENKINS] Archiving /home/ec2-user/jenkins/workspace/HBase-0.94/pom.xml to > /var/lib/jenkins/jobs/HBase-0.94/modules/org.apache.hbase$hbase/builds/2013-04-08_06-52-05/archive/org.apache.hbase/hbase/0.94.6/hbase-0.94.6.pom > Waiting for Jenkins to finish collecting data > mavenExecutionResult exceptions not empty > message : Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout > cause : Failure or timeout > Stack trace : > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test > (secondPartTestsExecution) on project hbase: Failure or timeout > [unhelpful big stacktrace] > channel stopped > Sending e-mails to: [email protected] > Finished: FAILURE > > It would be fantastic if the test(s) which timed out were listed somehow > here. > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
