[
https://issues.apache.org/jira/browse/HBASE-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647178#comment-13647178
]
Hadoop QA commented on HBASE-8469:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12581453/hbase-8472.v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5531//console
This message is automatically generated.
> [hadoop2] Several tests break because of HDFS-4305
> --------------------------------------------------
>
> Key: HBASE-8469
> URL: https://issues.apache.org/jira/browse/HBASE-8469
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 0.98.0, 0.94.6.1, 0.95.0
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Fix For: 0.98.0, 0.94.8, 0.95.1
>
> Attachments: hbase-8469.94.patch, hbase-8469.patch,
> hbase-8472.v2.patch
>
>
> Several unit tests will break due to HDFS-4305 (which enforces a min block
> size) because apprently, we set our block size smaller in these tests.
> {code}
> Specified block size is less than configured minimum value
> (dfs.namenode.fs-limits.min-block-size): 1024 < 1048576
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInt(FSNamesystem.java:1816)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFile(FSNamesystem.java:1795)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.create(NameNodeRpcServer.java:418)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.create(ClientNamenodeProtocolServerSideTranslatorPB.java:205)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java:44134)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1696)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1692)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:396)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1408)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:1690)
> {code}
> org.apache.hadoop.hbase.regionserver.TestHRegion.testgetHDFSBlocksDistribution
> org.apache.hadoop.hbase.regionserver.TestHRegionBusyWait.testgetHDFSBlocksDistribution
> org.apache.hadoop.hbase.replication.TestMasterReplication.testCyclicReplication
> org.apache.hadoop.hbase.replication.TestMasterReplication.testSimplePutDelete
> org.apache.hadoop.hbase.replication.TestMultiSlaveReplication.testMultiSlaveReplication
> org.apache.hadoop.hbase.util.TestFSUtils.testcomputeHDFSBlocksDistribution
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
