[
https://issues.apache.org/jira/browse/HADOOP-9585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675201#comment-13675201
]
Sanjay Radia commented on HADOOP-9585:
--------------------------------------
The error message for non existing files is normal. Appears that the only
failed test is the chgrp. Is the user id jenkins a member of the group admin?
> unit test failure :org.apache.hadoop.fs.TestFsShellReturnCode.testChgrp
> -----------------------------------------------------------------------
>
> Key: HADOOP-9585
> URL: https://issues.apache.org/jira/browse/HADOOP-9585
> Project: Hadoop Common
> Issue Type: Bug
> Components: test
> Affects Versions: 1.3.0
> Environment:
> https://builds.apache.org/job/Hadoop-branch1/lastCompletedBuild/testReport/org.apache.hadoop.fs/TestFsShellReturnCode/testChgrp/
> Reporter: Giridharan Kesavan
>
> Standard Error
> chmod: could not get status for
> '/home/jenkins/jenkins-slave/workspace/Hadoop-branch1/trunk/build/test/data/testChmod/fileDoesNotExist':
> File
> /home/jenkins/jenkins-slave/workspace/Hadoop-branch1/trunk/build/test/data/testChmod/fileDoesNotExist
> does not exist.
> chmod: could not get status for
> '/home/jenkins/jenkins-slave/workspace/Hadoop-branch1/trunk/build/test/data/testChmod/nonExistingfiles*'
> chown: could not get status for
> '/home/jenkins/jenkins-slave/workspace/Hadoop-branch1/trunk/build/test/data/testChown/fileDoesNotExist':
> File
> /home/jenkins/jenkins-slave/workspace/Hadoop-branch1/trunk/build/test/data/testChown/fileDoesNotExist
> does not exist.
> chown: could not get status for
> '/home/jenkins/jenkins-slave/workspace/Hadoop-branch1/trunk/build/test/data/testChown/nonExistingfiles*'
> chgrp: failed on
> 'file:/home/jenkins/jenkins-slave/workspace/Hadoop-branch1/trunk/build/test/data/testChgrp/fileExists':
> chgrp: changing group of
> `/home/jenkins/jenkins-slave/workspace/Hadoop-branch1/trunk/build/test/data/testChgrp/fileExists':
> Operation not permitted
--
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
