You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2016/03/21 23:49:25 UTC

[jira] [Created] (ZOOKEEPER-2395) allow ant command line control of junit test jvm args

Patrick Hunt created ZOOKEEPER-2395:
---------------------------------------

             Summary: allow ant command line control of junit test jvm args
                 Key: ZOOKEEPER-2395
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2395
             Project: ZooKeeper
          Issue Type: Improvement
          Components: build, tests
            Reporter: Patrick Hunt
            Assignee: Patrick Hunt
             Fix For: 3.4.9, 3.5.2, 3.6.0


We're seeing some failing jobs (see below) and the speculation is that it might be due to ipv6 vs ipv4 usage. It would be nice to turn on "prefer ipv4" in the jvm but there is no easy way to do that. I'll propose that we add a variable to ant that's passed through to the jvm.

----
This is very odd. It failed 2 of the last three times it was run on H9
with the following:

2016-03-20 06:06:18,480 [myid:] - INFO
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@74] - TEST METHOD FAILED
testBindByAddress
java.net.SocketException: No such device
at java.net.NetworkInterface.isLoopback0(Native Method)
at java.net.NetworkInterface.isLoopback(NetworkInterface.java:339)
at org.apache.zookeeper.test.ClientPortBindTest.testBindByAddress(ClientPortBindTest.java:61)

https://builds.apache.org/job/ZooKeeper_branch34/buildTimeTrend

Why would it pass one of the times though if there is no loopback
device on the host? That seems very odd!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)