Bug#852640: apache-mime4j: FTBFS randomly (failing tests)
Santiago Vila
sanvila at debian.org
Wed Jan 25 23:03:50 UTC 2017
Package: src:apache-mime4j
Version: 0.7.2-4
Severity: important
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:
--------------------------------------------------------------------------------
[...]
debian/rules build-indep
dh build-indep --buildsystem=maven --with javahelper
dh_testdir -i -O--buildsystem=maven
dh_update_autotools_config -i -O--buildsystem=maven
dh_auto_configure -i -O--buildsystem=maven
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 -plibapache-mime4j-java --debian-build --keep-pom-version --maven-repo=/<<PKGBUILDDIR>>/debian/maven-repo
jh_linkjars -i -O--buildsystem=maven
debian/rules override_dh_auto_build
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_auto_build -- install javadoc:aggregate
/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=/<<PKGBUILDDIR>> -Dclassworlds.conf=/etc/maven/m2-debian.conf org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<<PKGBUILDDIR>>/debian -Dmaven.repo.local=/<<PKGBUILDDIR>>/debian/maven-repo install javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
[... snipped ...]
Running org.apache.james.mime4j.dom.MessageServiceFactoryTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec - in org.apache.james.mime4j.dom.MessageServiceFactoryTest
Running org.apache.james.mime4j.dom.ExampleMessagesRoundtripTest
Tests run: 79, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.301 sec - in org.apache.james.mime4j.dom.ExampleMessagesRoundtripTest
Running org.apache.james.mime4j.dom.MessageCompleteMailTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec - in org.apache.james.mime4j.dom.MessageCompleteMailTest
Results :
Failed tests:
org.apache.james.mime4j.message.StringInputStreamTest#testBufferedRead AssertionFailedError
Tests run: 405, Failures: 1, Errors: 0, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache JAMES Mime4j Project ........................ SUCCESS [ 0.175 s]
[INFO] Apache JAMES Mime4j (Core) ......................... SUCCESS [ 6.578 s]
[INFO] Apache JAMES Mime4j (DOM) .......................... FAILURE [ 5.005 s]
[INFO] Apache JAMES Mime4j (Storage) ...................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 14.299 s
[INFO] Finished at: 2017-01-24T00:47:16+00:00
[INFO] Final Memory: 10M/27M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project apache-mime4j-dom: There are test failures.
[ERROR]
[ERROR] Please refer to /<<PKGBUILDDIR>>/dom/target/surefire-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :apache-mime4j-dom
dh_auto_test: /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=/<<PKGBUILDDIR>> -Dclassworlds.conf=/etc/maven/m2-debian.conf org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<<PKGBUILDDIR>>/debian -Dmaven.repo.local=/<<PKGBUILDDIR>>/debian/maven-repo test returned exit code 1
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
--------------------------------------------------------------------------------
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/apache-mime4j/
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.
The bug should be reproducible with sbuild on a single CPU virtual machine,
provided you try enough times (as the failure happens randomly).
Thanks.
More information about the pkg-java-maintainers
mailing list