[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821981#comment-15821981
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2664:
-------------------------------------------

GitHub user praste opened a pull request:

    https://github.com/apache/zookeeper/pull/148

    ZOOKEEPER-2664 Log4j2 migration

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/praste/zookeeper log4j2-migration

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zookeeper/pull/148.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #148
    
----
commit 6141943989c65519a8ddcb346aeda79f9cab81ae
Author: Pushkar Raste <pra...@bloomberg.net>
Date:   2016-12-20T22:47:24Z

    Log4j2 migration

commit f31eaa95e5ef3a884737dd7c1e56da8dea48c58c
Author: Pushkar Raste <pra...@bloomberg.net>
Date:   2016-12-20T22:48:17Z

    Log4j2 migration

commit 5770af750e90e09ab81a362ddcfbc6d25b6db2a5
Author: Pushkar Raste <pra...@bloomberg.net>
Date:   2017-01-04T19:57:11Z

    Log4j migration

commit 87f307592ca96c00e7c536f661715f8a6051de8d
Author: Pushkar Raste <pra...@bloomberg.net>
Date:   2017-01-04T22:32:16Z

    Log4j2 migration

commit fe072cee365c09e1fb1c5bb8df754c0da78cd471
Author: Pushkar Raste <pra...@bloomberg.net>
Date:   2017-01-05T21:00:23Z

    Log4j migration

commit 995277f5e80c998a0fa49fbd6b74ea53d7bf3468
Author: Pushkar Raste <pra...@bloomberg.net>
Date:   2017-01-13T16:35:49Z

    Log4j-migration Added disruptor dependency

commit 1d94d27f3caf29e9e582f9778ab79e10abaec35e
Author: Pushkar Raste <pra...@bloomberg.net>
Date:   2017-01-13T16:43:33Z

    Merge branch 'master' of https://github.com/apache/zookeeper into 
log4j2-migration

----


> ClientPortBindTest#testBindByAddress may fail due to "No such device" 
> exception
> -------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2664
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2664
>             Project: ZooKeeper
>          Issue Type: Test
>    Affects Versions: 3.4.6
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>         Attachments: ZOOKEEPER-2664.v1.txt
>
>
> Saw the following in a recent run:
> {code}
> Stacktrace
> java.net.SocketException: No such device
>       at java.net.NetworkInterface.isLoopback0(Native Method)
>       at java.net.NetworkInterface.isLoopback(NetworkInterface.java:390)
>       at 
> org.apache.zookeeper.test.ClientPortBindTest.testBindByAddress(ClientPortBindTest.java:61)
>       at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:52)
> Standard Output
> 2017-01-12 23:20:43,792 [myid:] - INFO  [main:ZKTestCase$1@50] - STARTING 
> testBindByAddress
> 2017-01-12 23:20:43,795 [myid:] - INFO  
> [main:JUnit4ZKTestRunner$LoggedInvokeMethod@50] - RUNNING TEST METHOD 
> testBindByAddress
> 2017-01-12 23:20:43,799 [myid:] - INFO  
> [main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED 
> testBindByAddress
> java.net.SocketException: No such device
>       at java.net.NetworkInterface.isLoopback0(Native Method)
>       at java.net.NetworkInterface.isLoopback(NetworkInterface.java:390)
>       at 
> org.apache.zookeeper.test.ClientPortBindTest.testBindByAddress(ClientPortBindTest.java:61)
>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>       at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>       at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>       at java.lang.reflect.Method.invoke(Method.java:601)
>       at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
>       at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>       at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
>       at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>       at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:52)
>       at org.junit.rules.TestWatchman$1.evaluate(TestWatchman.java:48)
>       at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
>       at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
>       at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
>       at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
>       at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
>       at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
>       at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
>       at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
>       at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:39)
>       at 
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:532)
>       at 
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1179)
>       at 
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:1030)
> {code}
> Proposed fix is to catch exception from isLoopback() call.



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

Reply via email to