[
https://issues.apache.org/jira/browse/HDFS-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767912#action_12767912
]
Hadoop QA commented on HDFS-679:
--------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12422640/appendToPartialChunk1.patch
against trunk revision 826905.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 9 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 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 passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/42/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/42/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/42/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/42/console
This message is automatically generated.
> Appending to a partial chunk incorrectly assumes the first packet fills up
> the partial chunk
> --------------------------------------------------------------------------------------------
>
> Key: HDFS-679
> URL: https://issues.apache.org/jira/browse/HDFS-679
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.21.0
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.21.0
>
> Attachments: appendToPartialChunk.patch, appendToPartialChunk1.patch
>
>
> When I run TestClientProtocolForPipelineRecovery, I always see that the block
> receiver throws IOException complaining about mismatched checksum when
> receiving the last data packet. It turns out the checksum of last packet was
> unexpectedly set to be zero.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
