hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3415) improve MiniMRYarnCluster & DistributedShell JAR resolution
Date Thu, 17 Nov 2011 19:05:51 GMT

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

Hadoop QA commented on MAPREDUCE-3415:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 14 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1318//console

This message is automatically generated.
> improve MiniMRYarnCluster & DistributedShell JAR resolution 
> ------------------------------------------------------------
>                 Key: MAPREDUCE-3415
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3415
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv2
>    Affects Versions: 0.24.0, 0.23.1
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>             Fix For: 0.24.0, 0.23.1
>         Attachments: MAPREDUCE-3415.patch, MAPREDUCE-3415.patch, MAPREDUCE-3415.patch,
> Current JAR resolution assumes the following:
> # The class used for JAR lookup is effectively in a JAR
> # A System property is set for testing with the location of the JAR
> The problem with #1 is that in some cases (when using the class in the same Maven module
where the class is, the class is not in a JAR but in a directory 'target/test-classes').
> The problem with #2 is the JAR does not exists at the time of running the test (packaging
comes after test and we are not doing integration testing yet thus won't work)
> In addition, this is required for streaming testcases, to have the JAR with streaming
classes for testing.

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