I assume that as a quick-fix solution it's safe to kill those processes in the post-build jenkins steps.
-Mikhail 2014-08-12 18:00 GMT-07:00, Ted Yu <[email protected]>: > Apache Jenkins sets surefire.secondPartThreadCount at 2 - so your build > should take shorter than Apache trunk build. > > Cheers > > > On Tue, Aug 12, 2014 at 5:30 PM, Alex Newman <[email protected]> wrote: > >> So I am trying to setup an internal jenkins. I have noticed, once >> builds complete (or fail), sometimes we have processes that stay >> around >> >> 20242 ? Sl 3:27 /usr/java/jdk1.7.0_55/jre/bin/java >> -enableassertions -XX:MaxDirectMemorySize=1G -Xmx1900m >> -XX:MaxPermSize=256m -Djava.security.egd=file:/dev/./urandom >> -Djava.net.preferIPv4Stack=true -Djava.awt.headless=true -jar >> >> /var/lib/jenkins/workspace/hbase_asf_master_box1/hbase-server/target/surefire/surefirebooter1201010766180838953.jar >> >> /var/lib/jenkins/workspace/hbase_asf_master_box1/hbase-server/target/surefire/surefire6309574441534864799tmp >> >> /var/lib/jenkins/workspace/hbase_asf_master_box1/hbase-server/target/surefire/surefire_2192766844117343368134tmp >> >> >> Our pre build maven step uses >> -DcompileSource=1.7 clean install -DskipTests to prepare the directory >> >> Then we run >> -PrunAllTests -DcompileSource=1.7 >> -Dmaven.test.redirectTestOutputToFile=true install >> -Dsurefire.secondPartThreadCount=5 -Dit.test=noItTest >> >> I am curious if this is a common problem. Any tricks we can do to speed >> this up? >> >> -Alex Newman >> > -- Thanks, Michael Antonov
