And, from HBASE-8280, it seems we don't use the same jvm for trunk and for precommit builds.
precommit build => *1.6* 13/04/05 14:29:02 INFO util.TestShowProperties: Property sun.boot.library.path=/home/jenkins/tools/java/jdk1.6.0_26/jre/lib/i386 13/04/05 14:29:02 INFO util.TestShowProperties: Property java.vm.version=20.1-b02 13/04/05 14:29:02 INFO util.TestShowProperties: Property java.vm.vendor=Sun Microsystems Inc. trunk build => *1.7* 13/04/05 15:22:13 INFO util.TestShowProperties: Property sun.boot.library.path=/x1/jenkins/tools/java/jdk1.7.0_04/jre/lib/amd64 13/04/05 15:22:13 INFO util.TestShowProperties: Property java.vm.version=23.0-b21 13/04/05 15:22:13 INFO util.TestShowProperties: Property java.vm.vendor=Oracle Corporation On Fri, Apr 5, 2013 at 5:29 PM, Nicolas Liochon <[email protected]> wrote: > Hi, > > It took me ages, but I found the difference between trunk and precommit > builds. > Precommits are executed on hadoop* machines. There is a single build at a > time. > Trunks are executed on ubuntu* machines. There are two simultaneous builds. > > For example, we have currently on ubuntu3: > ubuntu3 <https://builds.apache.org/computer/ubuntu3/> 1 > > core-integration-testing-maven-3-jdk-1.6<https://builds.apache.org/job/core-integration-testing-maven-3-jdk-1.6/> > > #639<https://builds.apache.org/job/core-integration-testing-maven-3-jdk-1.6/639/> > > > 2 > HBase-TRUNK <https://builds.apache.org/job/HBase-TRUNK/> > #4019<https://builds.apache.org/job/HBase-TRUNK/4019/> > > > > I suppose we can have two hbase builds on the same machine. > > Imho, that's why we have so many failures on trunk builds. > > Two solutions: > - Use hadoop* for trunk builds. That's the best option imho, they seem > cleaner then ubuntu* and less use. > - When building trunk, use a very low parallel test factor. May be 2. > > Thoughts? > Does anyone know how to do this? > > Nicolas > > >
