Your message dated Fri, 6 Jan 2017 12:49:55 +0100 with message-id <20170106114955.qheza7vsinwkvtwa@nuc> and subject line Re: Bug#850233: mavibot: FTBFS randomly (sbuild hangs) has caused the Debian Bug report #850233, regarding mavibot: FTBFS randomly (sbuild hangs) to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 850233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: src:mavibot Version: 1.0.0~M1-2 Severity: important Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed: -------------------------------------------------------------------------------- [...] debian/rules build-indep dh build-indep dh_testdir -i dh_update_autotools_config -i dh_autoreconf -i dh_auto_configure -i find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No such file or directory find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No such file or directory find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such file or directory mh_patchpoms -plibmavibot-java --debian-build --keep-pom-version --maven-repo=/<<BUILDDIR>>/mavibot-1.0.0\~M1/debian/maven-repo dh_auto_build -i /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<<BUILDDIR>>/mavibot-1.0.0\~M1 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<<BUILDDIR>>/mavibot-1.0.0\~M1/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<<BUILDDIR>>/mavibot-1.0.0\~M1/debian -Dmaven.repo.local=/<<BUILDDIR>>/mavibot-1.0.0\~M1/debian/maven-repo package -DskipTests -Dnotimestamp=true -Dlocale=en_US [INFO] Scanning for projects... [... snipped ...] Written 60000 elements in : 1018ms Written 70000 elements in : 1057ms Written 80000 elements in : 1068ms Written 90000 elements in : 1111ms Delta : 11530, nbError = 0, Nb insertion per second : 8000 6MB Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.88 sec - in org.apache.directory.mavibot.btree.RecordManagerFreePageTest Running org.apache.directory.mavibot.btree.BTreeConfigurationTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.048 sec - in org.apache.directory.mavibot.btree.BTreeConfigurationTest Running org.apache.directory.mavibot.btree.comparator.ByteArrayComparatorTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec - in org.apache.directory.mavibot.btree.comparator.ByteArrayComparatorTest Running org.apache.directory.mavibot.btree.comparator.ShortArrayComparatorTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec - in org.apache.directory.mavibot.btree.comparator.ShortArrayComparatorTest Running org.apache.directory.mavibot.btree.comparator.BooleanComparatorTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec - in org.apache.directory.mavibot.btree.comparator.BooleanComparatorTest Running org.apache.directory.mavibot.btree.comparator.CharArrayComparatorTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec - in org.apache.directory.mavibot.btree.comparator.CharArrayComparatorTest Running org.apache.directory.mavibot.btree.comparator.ShortComparatorTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec - in org.apache.directory.mavibot.btree.comparator.ShortComparatorTest Running org.apache.directory.mavibot.btree.comparator.LongComparatorTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec - in org.apache.directory.mavibot.btree.comparator.LongComparatorTest Running org.apache.directory.mavibot.btree.comparator.BooleanArrayComparatorTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec - in org.apache.directory.mavibot.btree.comparator.BooleanArrayComparatorTest Running org.apache.directory.mavibot.btree.comparator.ByteComparatorTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec - in org.apache.directory.mavibot.btree.comparator.ByteComparatorTest Running org.apache.directory.mavibot.btree.comparator.RevisionNameComparatorTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec - in org.apache.directory.mavibot.btree.comparator.RevisionNameComparatorTest Running org.apache.directory.mavibot.btree.comparator.LongArrayComparatorTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec - in org.apache.directory.mavibot.btree.comparator.LongArrayComparatorTest Running org.apache.directory.mavibot.btree.comparator.StringComparatorTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec - in org.apache.directory.mavibot.btree.comparator.StringComparatorTest Running org.apache.directory.mavibot.btree.comparator.CharComparatorTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in org.apache.directory.mavibot.btree.comparator.CharComparatorTest Running org.apache.directory.mavibot.btree.comparator.IntComparatorTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in org.apache.directory.mavibot.btree.comparator.IntComparatorTest Running org.apache.directory.mavibot.btree.comparator.IntArrayComparatorTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in org.apache.directory.mavibot.btree.comparator.IntArrayComparatorTest Running org.apache.directory.mavibot.btree.MultiThreadedBtreeTest Time to create 1M entries : 4 seconds Written 0 elements Written 100000 elements Written 200000 elements Written 300000 elements Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Thread-102" E: Build killed with signal TERM after 60 minutes of inactivity -------------------------------------------------------------------------------- This is just how the build ends, not necessarily the relevant part. I've put several build logs here: https://people.debian.org/~sanvila/build-logs/mavibot/ If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the page for this package. I don't know how to reproduce this, sorry, but it happened at least twice to me. If you try to reproduce it, please try many times. Thanks.
--- End Message ---
--- Begin Message ---On Fri, Jan 06, 2017 at 12:22:36PM +0100, Emmanuel Bourg wrote: > Le 5/01/2017 à 11:05, Santiago Vila a écrit : > > Running org.apache.directory.mavibot.btree.MultiThreadedBtreeTest > > Time to create 1M entries : 4 seconds > > Written 0 elements > > Written 100000 elements > > Written 200000 elements > > Written 300000 elements > > Exception: java.lang.OutOfMemoryError thrown from the > > UncaughtExceptionHandler in thread "Thread-102" > > > > I don't know how to reproduce this, sorry, but it happened at least twice > > to me. > > Hi Santiago, > > The tests ran out of memory. How much memory was assigned to the builder? Ooops! They were actually the smallest size I use: 768 MB of RAM plus 1 GB of swap. (I'm closing this bug with this message). I have a list of regexps to check for things like this. So I'll add another one for java.lang.OutOfMemoryError. But I still don't understand why it should fail. I measure the allocated memory by looking at Committed_AS in /proc/meminfo, and this package has never required more than 900 MB (less than 768MB + 1GB). Maybe it's the stack (not the heap, measured by Committed_AS) what my autobuilders had not enough? How could I ensure that this does not happen again in the general case? (Sorry if this is a stupid question, I don't know a lot about this low-level things). There is also another problem: I have at least one *successful* build containing an error like that (see attach). Is this not a violation of Policy 4.6? (That's the rule saying that whenever there is an error, the build should stop). Thanks a lot.
--- End Message ---
__ This is the maintainer address of Debian's Java team <http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use debian-j...@lists.debian.org for discussions and questions.
