hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-260) YARN tests have multiple failures on Windows due to "Queue configuration missing"
Date Mon, 10 Dec 2012 21:09:21 GMT

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

Chris Nauroth commented on YARN-260:

We'll need to resolve multiple issues to get the trunk streaming tests working on Windows:

# {{TestStreaming}} tries to set up input and output paths for HDFS based on the local test
directory, including drive spec.  This gets rejected, because ':' is invalid in HDFS file
names.  We'll need to check for Windows in {{TestStreaming}} and strip off the drive spec.
# When {{DefaultContainerExecutor#launchContainer}} creates the container command array, the
result may include a leading slash before the drive spec, which Windows won't allow.  This
can be solved using {{Path#toString}}, which already has the logic for removing the leading
slash on Windows if it has a drive spec.
# Getting past all of that, container launch still fails, because the log output of {{StreamJob}}
shows that we are generating command lines that exceed the Windows maximum (~8000 characters).

> YARN tests have multiple failures on Windows due to "Queue configuration missing"
> ---------------------------------------------------------------------------------
>                 Key: YARN-260
>                 URL: https://issues.apache.org/jira/browse/YARN-260
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: applications
>    Affects Versions: trunk-win
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
> There are multiple test failures due to "Queue configuration missing child queue names
for root".

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

View raw message