On 2010-08-17, Stefan Bodewig wrote:

> After the Gump run was finished there still where about ten or fifteen
> java processes active, all of them running
> surefire-booter-something.jar.  They may be leftovers from when Gump
> terminates a build process, I'll keep an eye on it.

The last Gump run just finished:

,----
| g...@vmgump:~$ ps auxww | fgrep java
| gump      5959  0.5  7.8 1453756 80504 ?       Sl   03:20   0:18 
/usr/lib/jvm/java-6-openjdk/jre/bin/java -Xmx1024m -jar 
/tmp/surefirebooter7599168861280918845.jar /tmp/surefire4707031424830803939tmp 
/tmp/surefire7549294063188826154tmp
| gump      9115  0.0  0.0   7576   780 pts/0    S+   04:13   0:00 fgrep java
| g...@vmgump:~$ free
|              total       used       free     shared    buffers     cached
| Mem:       1023600     802964     220636          0     290976     305260
| -/+ buffers/cache:     206728     816872
| Swap:      2187256     114768    2072488
| g...@vmgump:~$ kill -9 5959
| g...@vmgump:~$ free
|              total       used       free     shared    buffers     cached
| Mem:       1023600     714852     308748          0     291000     305032
| -/+ buffers/cache:     118820     904780
| Swap:      2187256      31120    2156136
`----

The project built at 3:20 has been apacheds-server-integ-test and it
failed because

,----
| [INFO] Error while executing forked tests.; nested exception is 
org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineTimeOutException:
 Error while executing external command, process killed.
| 
| Process timeout out after 900 seconds
`----

so it is mvn not Gump that is killing processes and leaving some undeads
behind.

I'll play around with Gump's support for running a shell script after a
Gump run in order to kill any surefirebooter java processes still alive.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Reply via email to