[
https://issues.apache.org/jira/browse/HADOOP-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598876#action_12598876
]
Hadoop QA commented on HADOOP-3419:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12382419/HADOOP-fixtestfsck-2.patch
against trunk revision 658862.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 4 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 passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2511/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2511/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2511/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2511/console
This message is automatically generated.
> TestFsck fails once in a while on WINDOWS/LINUX
> -----------------------------------------------
>
> Key: HADOOP-3419
> URL: https://issues.apache.org/jira/browse/HADOOP-3419
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.0
> Environment: Windows, LINUX
> Reporter: lohit vijayarenu
> Assignee: lohit vijayarenu
> Fix For: 0.18.0
>
> Attachments: HADOOP-fixtestfsck-2.patch, HADOOP-fixtestfsck.patch
>
>
> Once in a while, TestFsck seemed to fail on Windows. After running the test
> in a loop for 25 times, I could see it fail 2 or so times even in LINUX.
> Looks like getBlockLocations was being called few places even before files
> created on dfs had been replicated. And some times, we corrupt block even
> before it had been replicated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
