Bug#840827: lucene-solr: Network tests are performed using public IP instead of 127.0.0.1

Santiago Vila sanvila at debian.org
Mon Oct 24 16:46:19 UTC 2016


retitle 840827 lucene-solr: Network tests are performed using public IP instead of 127.0.0.1
severity 840827 normal
thanks

On Mon, Oct 24, 2016 at 05:08:39PM +0200, Emmanuel Bourg wrote:

> 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?

Big ooops! Sorry. That was why it failed.

Not all my machines have a fixed IP, and I made the mistake of putting
the public IP of the day in /etc/hosts instead of 127.0.1.1.

I've triggered rebuilds on the machines where it previously failed and
now it does not fail, so there is no FTBFS bug anymore.



But I have still to "redact" the build logs in case the tests fail.

Would not be better to do the tests by connecting to localhost or
127.0.0.1 instead of the machine name?

I think this would even simplify the code, as you could use always
"localhost" instead of having to guess the real hostname first.


Thanks a lot.



More information about the pkg-java-maintainers mailing list