[
https://issues.apache.org/jira/browse/HADOOP-5654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698064#action_12698064
]
Hadoop QA commented on HADOOP-5654:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12405183/testReplicationPolicy.patch
against trunk revision 764085.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/183/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/183/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/183/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/183/console
This message is automatically generated.
> TestReplicationPolicy.<init> fails on java.net.BindException
> ------------------------------------------------------------
>
> Key: HADOOP-5654
> URL: https://issues.apache.org/jira/browse/HADOOP-5654
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Reporter: Hairong Kuang
> Fix For: 0.21.0
>
> Attachments: testReplicationPolicy.patch
>
>
> java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind(Native Method)
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
> at
> org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:216)
> at org.apache.hadoop.http.HttpServer.start(HttpServer.java:422)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.startHttpServer(NameNode.java:330)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.activate(NameNode.java:277)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:269)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:373)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:367)
> at
> org.apache.hadoop.hdfs.server.namenode.TestReplicationPolicy.<clinit>(TestReplicationPolicy.java:58)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:169)
> at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:335)
> at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:911)
> at
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:768)
> Looks that it was caused by another running unit test. They used the same
> http server port.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
