hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-449) MRAppMaster classpath not set properly for unit tests in downstream projects
Date Wed, 06 Mar 2013 05:14:15 GMT

    [ https://issues.apache.org/jira/browse/YARN-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594377#comment-13594377
] 

Ted Yu commented on YARN-449:
-----------------------------

I tried the following change:
{code}
Index: hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java
===================================================================
--- hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java	(revision
1453107)
+++ hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java	(working copy)
@@ -1578,6 +1578,7 @@
     mrCluster = new MiniMRCluster(servers,
       FS_URI != null ? FS_URI : FileSystem.get(conf).getUri().toString(), 1,
       null, null, new JobConf(this.conf));
+    this.conf = mrCluster.createJobConf();
     JobConf jobConf = MapreduceTestingShim.getJobConf(mrCluster);
     if (jobConf == null) {
       jobConf = mrCluster.createJobConf();
{code}
mapreduce.TestTableMapReduce#testMultiRegionTable hangs running against hadoop 1.0
                
> MRAppMaster classpath not set properly for unit tests in downstream projects
> ----------------------------------------------------------------------------
>
>                 Key: YARN-449
>                 URL: https://issues.apache.org/jira/browse/YARN-449
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.0.3-alpha
>            Reporter: Siddharth Seth
>            Priority: Blocker
>         Attachments: hbase-TestHFileOutputFormat-wip.txt, hbase-TestingUtility-wip.txt
>
>
> Post YARN-429, unit tests for HBase continue to fail since the classpath for the MRAppMaster
is not being set correctly.
> Reverting YARN-129 may fix this, but I'm not sure that's the correct solution. My guess
is, as Alexandro pointed out in YARN-129, maven classloader magic is messing up java.class.path.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message