You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Akira AJISAKA (JIRA)" <ji...@apache.org> on 2014/07/11 08:36:05 UTC
[jira] [Commented] (MAPREDUCE-4253) Tests for mapreduce-client-core
are lying under mapreduce-client-jobclient
[ https://issues.apache.org/jira/browse/MAPREDUCE-4253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058474#comment-14058474 ]
Akira AJISAKA commented on MAPREDUCE-4253:
------------------------------------------
This issue causes the problem that when the code in mapreduce-client-core changes, Jenkins doesn't sometimes run the right test code, which is in mapreduce-client-jobclient.
Therefore I'd like to fix this issue. [~ozawa] and [~qwertymaniac], what's going on this issue?
> Tests for mapreduce-client-core are lying under mapreduce-client-jobclient
> --------------------------------------------------------------------------
>
> Key: MAPREDUCE-4253
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4253
> Project: Hadoop Map/Reduce
> Issue Type: Task
> Components: client
> Affects Versions: 2.0.0-alpha
> Reporter: Harsh J
> Assignee: Tsuyoshi OZAWA
> Fix For: 2.4.0
>
> Attachments: MR-4253.1.patch, MR-4253.2.patch, crossing_project_checker.rb, result.txt
>
>
> Many of the tests for client libs from mapreduce-client-core are lying under mapreduce-client-jobclient.
> We should investigate if this is the right thing to do and if not, move the tests back into client-core.
--
This message was sent by Atlassian JIRA
(v6.2#6252)