Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 17 Jun 2013 20:44:20 +0000 (UTC)
From: "Chris Nauroth (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12653139.1371454041393.127804.1371501860377@arcas>
In-Reply-To: <JIRA.12653139.1371454041393@arcas>
References: <JIRA.12653139.1371454041393@arcas>
Subject: [jira] [Updated] (YARN-839)
 TestContainerLaunch.testContainerEnvVariables fails on Windows
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Nauroth updated YARN-839:
-------------------------------

    Attachment: YARN-839-branch-2.2.patch

This looks good, Chuan.  I confirmed that the test passes on both Mac and Windows for both trunk and branch-2.

Once again, there was a minor formatting difference between trunk and branch-2.  I'm attaching a new version of the branch-2 patch that removes some unused imports and changes some spacing.  This will make the file identical between trunk and branch-2.  Does this still look good to you?  If so, then I'll commit it.
                
> TestContainerLaunch.testContainerEnvVariables fails on Windows
> --------------------------------------------------------------
>
>                 Key: YARN-839
>                 URL: https://issues.apache.org/jira/browse/YARN-839
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 3.0.0, 2.1.0-beta
>            Reporter: Chuan Liu
>            Assignee: Chuan Liu
>            Priority: Minor
>         Attachments: YARN-839-branch-2.2.patch, YARN-839-branch-2.patch, YARN-839.patch
>
>
> The unit test case fails on Windows due to job id or container id was not printed out as part of the container script. Later, the test tries to read the pid from output of the file, and fails.
> Exception in trunk:
> {noformat}
> Running org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.TestContainerLaunch
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 9.903 sec <<< FAILURE!
> testContainerEnvVariables(org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.TestContainerLaunch)  Time elapsed: 1307 sec  <<< ERROR!
> java.lang.NullPointerException
>         at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.TestContainerLaunch.testContainerEnvVariables(TestContainerLaunch.java:278)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>         at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>         at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>         at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>         at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:62)
> {noformat}

--
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