hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3427) streaming tests fail with MR2
Date Wed, 01 Feb 2012 23:39:53 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198328#comment-13198328

Hudson commented on MAPREDUCE-3427:

Integrated in Hadoop-Hdfs-0.23-Commit #454 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Commit/454/])
    Merge -c 1239391 from trunk to branch-0.23 to fix MAPREDUCE-3427. Fix streaming unit tests
broken after mavenization.

acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1239392
Files : 
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-tools/hadoop-streaming/pom.xml
* /hadoop/common/branches/branch-0.23/hadoop-tools/hadoop-streaming/src/test/java/org/apache/hadoop/streaming/TestStreamingBadRecords.java
* /hadoop/common/branches/branch-0.23/hadoop-tools/hadoop-streaming/src/test/java/org/apache/hadoop/streaming/TestUlimit.java

> streaming tests fail with MR2
> -----------------------------
>                 Key: MAPREDUCE-3427
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3427
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: contrib/streaming, mrv2
>    Affects Versions: 0.23.1, 0.24.0
>            Reporter: Alejandro Abdelnur
>            Assignee: Hitesh Shah
>            Priority: Blocker
>             Fix For: 0.23.1
>         Attachments: MR-3427.1.patch
> After Mavenizing streaming and getting its testcases to use the MiniMRCluster wrapper
(MAPREDUCE-3169), 4 testcases fail to pass.
> Following is an assessment of those failures. Note that the testcases have been tweaked
only to set the streaming JAR and yarn as the  framework.
> (If these issues are unrelated we should create sub-tasks for each one of them).
> *TestStreamingCombiner*, fails because returned counters don't match assertion. However,
counters printed in the test output indicate values that would satisfy the assertion. As Tom
has indicated it seems MR/YARN are not passing back counter information to the client API.
> *TestStreamingBadRecords*, the job is failing with the following exception
> {code}
> Application application_1321575850006_0001 failed 1 times due to AM Container for 
> appattempt_1321575850006_0001_000001 exited with  exitCode: 127 due to: 
> .Failing this attempt.. Failing the application.
> {code}
> Difficult to troubleshoot because there are not task logs from Mini MR/YARN  run.
> *TestStreamingStatus* fails in validateTaskStatus() in the following assertion
> {code}
> expected:<[before consuming input > sort]> but was:<[SUCCEEDED]>
> {code}
> *TestUlimit* fails with
> {code}
> org.junit.ComparisonFailure: output is wrong expected:<[786432]> but was:<[unlimited]>
> {code}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message