FYI, I changed the top-level testsuite module to use the shitty-maven-
plugin to invoke the children *-testsuite modules, which forks off
another mvn process for each and seems to hang less due to weird ant/
maven/groovy/whatever gremlins.
I'm also doing a test now of using just one geronimo:start-server (and
selenium bits) at the very top-level to see if that improves the time
to run the testsuite... and doesn't cause weird problems.
--jason
On May 7, 2008, at 3:56 PM, [EMAIL PROTECTED] wrote:
Geronimo Revision: 654010 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 37 minutes 24 seconds
[INFO] Finished at: Wed May 07 03:44:43 EDT 2008
[INFO] Final Memory: 334M/703M
[INFO]
------------------------------------------------------------------------
TESTSUITE RESULTS (Failures only)
=================================
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=================================
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/logs-0300-tomcat/test.log
Assembly: jetty
=================================
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/logs-0300-jetty/test.log
Samples: trunk
=================================
Log:
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080507/samples-0300.log
Build status: OK
