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

Hadoop QA commented on HDFS-4104:
---------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12551406/hdfs4104-3.txt
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HDFS-Build/3429//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3429//console

This message is automatically generated.
                
> dfs -test -d prints inappropriate error on nonexistent directory
> ----------------------------------------------------------------
>
>                 Key: HDFS-4104
>                 URL: https://issues.apache.org/jira/browse/HDFS-4104
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.0.2-alpha
>            Reporter: Andy Isaacson
>            Assignee: Andy Isaacson
>            Priority: Minor
>         Attachments: hdfs4104-2.txt, hdfs4104-3.txt, hdfs-4104.txt
>
>
> Running {{hdfs dfs -test -d foo}} should return 0 or 1 as appropriate. It 
> should not generate any output due to missing files.  Alas, it prints an 
> error message when {{foo}} does not exist.
> {code}
> $ hdfs dfs -test -d foo; echo $?
> test: `foo': No such file or directory
> 1
> {code}

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

Reply via email to