Bug#840827: lucene-solr: FTBFS (failing tests, no route to host)

2016-10-24 Thread Emmanuel Bourg 
Hi Santiago,

I got a look at this issue and it seems the failing tests are setting up
a local RMI server but the subsequent connections do not work.

I don't know why it fails with your machines but if I'm not mistaken
local connections are allowed during the build.

Is the IP you redacted the one from the machine building the package, or
another machine on your network?

Is it possible that the tests hit a TCP connection limit on the host?

Emmanuel Bourg

Bug#840827: lucene-solr: FTBFS (failing tests, no route to host)

2016-10-15 Thread Santiago Vila 
I forgot to tell that I can reproduce this only on some machines but
not in others. The machines on which it fails (there are more than one)
seem to be the ones having some corporate firewall rules I can't
disable. This is probably not just a coincidence.

However, since packages are not supposed to use the network during the build,
a bad network configuration should never make the package to FTBFS anyway.

Thanks.

Bug#840827: lucene-solr: FTBFS (failing tests, no route to host)

2016-10-15 Thread Santiago Vila 
Package: src:lucene-solr
Version: 3.6.2+dfsg-8
Severity: serious

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 --with maven_repo_helper
   dh_testdir -i
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/lucene-solr-3.6.2+dfsg'
# Link in jars from /usr/share/java rather
# than patching the build process
for pkg in `cat debian/build-jars`; \
do \
ln -sf `echo $pkg | cut -d : -f 1` `echo $pkg | cut -d : -f 2`; \
done
ln: failed to create symbolic link './lucene/lib/ant.jar': No such file or 
directory

[... snipped ...]

[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:535)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1182)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:1033)
[junit] Caused by: java.net.NoRouteToHostException: No route to host
[junit] at java.net.PlainSocketImpl.socketConnect(Native Method)
[junit] at 
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
[junit] at 
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
[junit] at 
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
[junit] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
[junit] at java.net.Socket.connect(Socket.java:589)
[junit] at java.net.Socket.connect(Socket.java:538)
[junit] at java.net.Socket.(Socket.java:434)
[junit] at java.net.Socket.(Socket.java:211)
[junit] at 
sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40)
[junit] at 
sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:148)
[junit] at 
sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)
[junit] ... 44 more
[junit] 
[junit] 
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 5.301 sec
[junit] 
[junit] - Standard Error -
[junit] NOTE: reproduce with: ant test 
-Dtestcase=TestRemoteCachingWrapperFilter -Dtestmethod=testTermRemoteFilter 
-Dtests.seed=360d91d04c9e1cb5:-d1bf13dc331d343:-5a995359e653cf8b 
-Dargs="-Dfile.encoding=ANSI_X3.4-1968"
[junit] NOTE: reproduce with: ant test 
-Dtestcase=TestRemoteCachingWrapperFilter -Dtestmethod=testTermRemoteFilter 
-Dtests.seed=360d91d04c9e1cb5:-d1bf13dc331d343:-5a995359e653cf8b 
-Dargs="-Dfile.encoding=ANSI_X3.4-1968"
[junit] NOTE: test params are: locale=it, timezone=Pacific/Enderbury
[junit] NOTE: all tests run in this JVM:
[junit] [TestRemoteCachingWrapperFilter]
[junit] NOTE: Linux 4.7.0-1-amd64 amd64/Oracle Corporation 1.8.0_102 
(64-bit)/cpus=1,threads=1,free=86734984,total=95354880
[junit] -  ---
[junit] Test org.apache.lucene.search.TestRemoteCachingWrapperFilter FAILED

BUILD FAILED
/<>/lucene-solr-3.6.2+dfsg/lucene/build.xml:584: The following error 
occurred while executing this line:
/<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:1051: The 
following error occurred while executing this line:
/<>/lucene-solr-3.6.2+dfsg/lucene/contrib/contrib-build.xml:61: The 
following error occurred while executing this line:
/<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:692: 
The following error occurred while executing this line:
/<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:676: Tests failed!
The following error occurred while executing this line:
/<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:676: Tests failed!
The following error occurred while executing this line:
/<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:676: Tests failed!
The following error occurred while executing this line:
/<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:676: Tests failed!

Total time: 10 minutes 58 seconds
debian/rules:31: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>/lucene-solr-3.6.2+dfsg'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The build was made in a KVM/QEMU virtual machine with 1 CPU using sbuild.

I attach a full build log, but the build system leaks the IP of the machine
(it probably shouldn't). I've redacted that.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still