[
https://issues.apache.org/jira/browse/MAPREDUCE-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073943#comment-14073943
]
Manu Zhang commented on MAPREDUCE-5991:
---------------------------------------
[~tlipcon][~decster], how am I supposed to run a scenario test now ?
I've tried "mvn test -Dtest=CompressTest" and "mvn test -Dtest=CompressTest
-Pnative" but both failed with "Cannot initialize Cluster. Please check your
configuration for mapreduce.framework.name and the correspond server adresses"
exception.
Removing the "test-jar" type of "hadoop-mapreduce-client-common" would work. I
think tests depend on hadoop-mapreduce-client-common for LocalJobRunner.
> native-task should not run unit tests if native profile is not enabled
> ----------------------------------------------------------------------
>
> Key: MAPREDUCE-5991
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5991
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: task
> Reporter: Todd Lipcon
> Assignee: Binglin Chang
> Attachments: MAPREDUCE-5991.v1.patch
>
>
> Currently, running "mvn test" without the 'native' profile enabled causes all
> of the native-task tests to fail. In order to integrate to trunk, we need to
> fix this - either using JUnit "Assume" commands in each test that depends on
> native code, or disabling the tests from the pom unless -Pnative is specified
--
This message was sent by Atlassian JIRA
(v6.2#6252)
