You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2012/10/22 21:06:12 UTC
[jira] [Created] (HADOOP-8955) "chmod" executable not found on
Windows
Chris Nauroth created HADOOP-8955:
-------------------------------------
Summary: "chmod" executable not found on Windows
Key: HADOOP-8955
URL: https://issues.apache.org/jira/browse/HADOOP-8955
Project: Hadoop Common
Issue Type: Bug
Components: fs
Affects Versions: trunk-win
Reporter: Chris Nauroth
Assignee: Chris Nauroth
Hadoop Common attempts to call the "chmod" executable, which isn't available on Windows.
--
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
[jira] [Commented] (HADOOP-8955) "chmod" executable not found on
Windows
Posted by "Chris Nauroth (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481668#comment-13481668 ]
Chris Nauroth commented on HADOOP-8955:
---------------------------------------
The failing test suites are:
org.apache.hadoop.fs.TestLocalDirAllocator
org.apache.hadoop.util.TestDiskChecker
Both test suites have hard-coded calls to chmod that need to be rerouted through winutils on Windows. On branch-1-win, TestLocalDirAllocator was changed to skip a few tests on Windows.
{code}
testLocalPathForWriteDirCreation[0](org.apache.hadoop.fs.TestLocalDirAllocator) Time elapsed: 78 sec <<< ERROR!
java.io.IOException: Cannot run program "chmod": CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)
at org.apache.hadoop.util.Shell.runCommand(Shell.java:194)
at org.apache.hadoop.util.Shell.run(Shell.java:169)
at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:374)
at org.apache.hadoop.util.Shell.execCommand(Shell.java:463)
at org.apache.hadoop.util.Shell.execCommand(Shell.java:446)
at org.apache.hadoop.fs.TestLocalDirAllocator.testLocalPathForWriteDirCreation(TestLocalDirAllocator.java:291)
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:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:24)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)
... 43 more
{code}
> "chmod" executable not found on Windows
> ---------------------------------------
>
> Key: HADOOP-8955
> URL: https://issues.apache.org/jira/browse/HADOOP-8955
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: trunk-win
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
>
> Hadoop Common attempts to call the "chmod" executable, which isn't available on Windows.
--
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
[jira] [Resolved] (HADOOP-8955) "chmod" executable not found on
Windows
Posted by "Suresh Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Srinivas resolved HADOOP-8955.
-------------------------------------
Resolution: Fixed
Fix Version/s: trunk-win
Hadoop Flags: Reviewed
I committed the patch to branch-trunk-win. Thank you Chris.
> "chmod" executable not found on Windows
> ---------------------------------------
>
> Key: HADOOP-8955
> URL: https://issues.apache.org/jira/browse/HADOOP-8955
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: trunk-win
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Fix For: trunk-win
>
> Attachments: HADOOP-8955-branch-trunk-win.patch
>
>
> Hadoop Common attempts to call the "chmod" executable, which isn't available on Windows.
--
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
[jira] [Updated] (HADOOP-8955) "chmod" executable not found on
Windows
Posted by "Chris Nauroth (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Nauroth updated HADOOP-8955:
----------------------------------
Attachment: HADOOP-8955-branch-trunk-win.patch
This patch fixes the chmod failures by changing the tests to use the Shell API instead of calling chmod directly.
TestDiskChecker fails for a different reason now, which we'll need to address in a separate jira.
> "chmod" executable not found on Windows
> ---------------------------------------
>
> Key: HADOOP-8955
> URL: https://issues.apache.org/jira/browse/HADOOP-8955
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: trunk-win
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: HADOOP-8955-branch-trunk-win.patch
>
>
> Hadoop Common attempts to call the "chmod" executable, which isn't available on Windows.
--
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
[jira] [Commented] (HADOOP-8955) "chmod" executable not found on
Windows
Posted by "Suresh Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484150#comment-13484150 ]
Suresh Srinivas commented on HADOOP-8955:
-----------------------------------------
+1 for the patch
> "chmod" executable not found on Windows
> ---------------------------------------
>
> Key: HADOOP-8955
> URL: https://issues.apache.org/jira/browse/HADOOP-8955
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: trunk-win
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: HADOOP-8955-branch-trunk-win.patch
>
>
> Hadoop Common attempts to call the "chmod" executable, which isn't available on Windows.
--
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
[jira] [Commented] (HADOOP-8955) "chmod" executable not found on
Windows
Posted by "Chris Nauroth (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483532#comment-13483532 ]
Chris Nauroth commented on HADOOP-8955:
---------------------------------------
This also impacts:
org.apache.hadoop.streaming.TestStreamingTaskLog
> "chmod" executable not found on Windows
> ---------------------------------------
>
> Key: HADOOP-8955
> URL: https://issues.apache.org/jira/browse/HADOOP-8955
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: trunk-win
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
>
> Hadoop Common attempts to call the "chmod" executable, which isn't available on Windows.
--
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