[
https://issues.apache.org/jira/browse/HADOOP-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639258#action_12639258
]
Hadoop QA commented on HADOOP-4403:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12392035/4403_20081013.patch
against trunk revision 704261.
+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 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/Hadoop-Patch/3452/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3452/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3452/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3452/console
This message is automatically generated.
> TestLeaseRecovery.testBlockSynchronization failed on trunk
> ----------------------------------------------------------
>
> Key: HADOOP-4403
> URL: https://issues.apache.org/jira/browse/HADOOP-4403
> Project: Hadoop Core
> Issue Type: Test
> Components: dfs, test
> Reporter: Hemanth Yamijala
> Assignee: Tsz Wo (Nicholas), SZE
> Priority: Blocker
> Fix For: 0.18.2, 0.19.0
>
> Attachments: 4403_20081013.patch
>
>
> TestLeaseRecovery.testBlockSynchronization failed on a hadoop patch build.
> Please refer to
> http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3450/testReport/org.apache.hadoop.hdfs/TestLeaseRecovery/testBlockSynchronization/
> for details. I don't know if it is a random issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
