hadoop-yarn-issues mailing list archives

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

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

Siddharth Seth commented on YARN-449:
-------------------------------------

Ted, are all these tests passing against 2.0.2-alpha ? That seems like the first thing that
should be addressed - did something changed in 2.0.3 which causes them to fail.
Also, does HBase run tests in parallel ? Three different tests failing in different test-runs
on the build box could be caused by this. Looking at the way MiniMRCluster works, the work-dir
ends up being the same across tests - so that can be problematic. (Attaching a wip patch for
this which I've tested on a couple of HBase tests - running individually). Would it be possible
for you to try the patch on a box where you're seeing failures.
>From running the three tests locally - TestImportExport consistently hangs. The other
two seem to work ok.
                
> 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: 7904-v5.txt, hbase-7904-v3.txt, 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