[jira] [Commented] (ZOOKEEPER-2395) allow ant command line control of junit test jvm args
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15839502#comment-15839502 ] Edward Ribeiro commented on ZOOKEEPER-2395: --- oops, *excuse me* [~hanm] for skipping this comment on ZK-2664, shame on me. :( Agree with you. > 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.5.3, 3.6.0, 3.4.11 > > > 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)
[jira] [Commented] (ZOOKEEPER-2395) allow ant command line control of junit test jvm args
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15839037#comment-15839037 ] Michael Han commented on ZOOKEEPER-2395: I think I've commented this in ZOOKEEPER-2664... I have no objections to close this one though, but just want to point out that "allow ant command line control of junit test jvm args" could potentially benefit debugging tests. > 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.5.3, 3.6.0, 3.4.11 > > > 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)
[jira] [Commented] (ZOOKEEPER-2395) allow ant command line control of junit test jvm args
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837645#comment-15837645 ] Edward Ribeiro commented on ZOOKEEPER-2395: --- [~hanm], is this issue a duplicate of ZOOKEEPER-2664? I think so, and if I am right we should close it, right? Do you agree [~phunt]? > 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.10, 3.5.3, 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)
[jira] [Commented] (ZOOKEEPER-2395) allow ant command line control of junit test jvm args
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15205320#comment-15205320 ] Patrick Hunt commented on ZOOKEEPER-2395: - Chris suggested: I vaguely recall that this kind of stack trace can happen with certain combinations of IPv6 enabled and the host OS doing unexpected things in the entry for the loopback address in /etc/hosts. (Java parses /etc/hosts as part of looking at the network interface information.) Sorry, but I don't remember the specifics. Hadoop runs its tests with -Djava.net.preferIPv4Stack=true. Maybe we should try the same? > 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)
