You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2008/09/23 09:40:44 UTC
[jira] Commented: (HADOOP-4237)
TestStreamingBadRecords.testNarrowDown fails intermittently
[ https://issues.apache.org/jira/browse/HADOOP-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633643#action_12633643 ]
Hadoop QA commented on HADOOP-4237:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12390639/4237_v1.patch
against trunk revision 697306.
+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 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/3350/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3350/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3350/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3350/console
This message is automatically generated.
> TestStreamingBadRecords.testNarrowDown fails intermittently
> -----------------------------------------------------------
>
> Key: HADOOP-4237
> URL: https://issues.apache.org/jira/browse/HADOOP-4237
> Project: Hadoop Core
> Issue Type: Test
> Components: contrib/streaming, test
> Affects Versions: 0.19.0
> Reporter: Sharad Agarwal
> Assignee: Sharad Agarwal
> Priority: Minor
> Fix For: 0.19.0
>
> Attachments: 4237_v1.patch
>
>
> TestStreamingBadRecords.testNarrowDown is failing sometimes because of the delay in the processed counter updation (processed counter updation happens by the separate thread). Due to this there is a broader skipped range to be narrow down. The no of attempts provided in the test case get exhausted before completing the task successfully.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.