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 "Sharad Agarwal (JIRA)" <ji...@apache.org> on 2008/09/22 12:24:44 UTC

[jira] Created: (HADOOP-4237) TestStreamingBadRecords.testNarrowDown fails intermittently

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
    Affects Versions: 0.19.0
            Reporter: Sharad Agarwal
            Assignee: Sharad Agarwal
            Priority: Minor
             Fix For: 0.19.0


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.


[jira] Updated: (HADOOP-4237) TestStreamingBadRecords.testNarrowDown fails intermittently

Posted by "Nigel Daley (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nigel Daley updated HADOOP-4237:
--------------------------------

    Component/s: test

> 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.


[jira] Updated: (HADOOP-4237) TestStreamingBadRecords.testNarrowDown fails intermittently

Posted by "Sharad Agarwal (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sharad Agarwal updated HADOOP-4237:
-----------------------------------

    Attachment: 4237_v1.patch

straight forward patch.
- increased the no of map/reduce attempts
- removed the task timeout case, as it was making the test case to take lot of time and is already covered in TestBadRecords.

> 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
>    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.


[jira] Commented: (HADOOP-4237) TestStreamingBadRecords.testNarrowDown fails intermittently

Posted by "Sharad Agarwal (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634032#action_12634032 ] 

Sharad Agarwal commented on HADOOP-4237:
----------------------------------------

test failure not related to this patch.

> 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.


[jira] Commented: (HADOOP-4237) TestStreamingBadRecords.testNarrowDown fails intermittently

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Updated: (HADOOP-4237) TestStreamingBadRecords.testNarrowDown fails intermittently

Posted by "Sharad Agarwal (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sharad Agarwal updated HADOOP-4237:
-----------------------------------

    Status: Patch Available  (was: Open)

> 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.


[jira] Updated: (HADOOP-4237) TestStreamingBadRecords.testNarrowDown fails intermittently

Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Devaraj Das updated HADOOP-4237:
--------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]
          Status: Resolved  (was: Patch Available)

I just committed this. Thanks, Sharad!

> 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.


[jira] Commented: (HADOOP-4237) TestStreamingBadRecords.testNarrowDown fails intermittently

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635413#action_12635413 ] 

Hudson commented on HADOOP-4237:
--------------------------------

Integrated in Hadoop-trunk #618 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/618/])

> 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.