[
https://issues.apache.org/jira/browse/HADOOP-9582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683829#comment-13683829
]
Ashwin Shankar commented on HADOOP-9582:
----------------------------------------
{quote}
TestGenericOptionsParser change now seems moot, since we didn't modify
GenericOptionsParser and it doesn't test the FsShell change.
{quote}
Yes,right. I've reverted that change in the latest patch.
{quote}
Nit: In TestFsShell rather than wielding AssertionFailedError directly we can
simply use assertTrue(th instanceof RuntimeException)
{quote}
I did do this in one my previous patch,however Steve(on 22/May/13 06:01)
recommended that raising AssertionFailedError would be better for diagnostics.
Should I still use assertTrue ?
> Non-existent file to "hadoop fs -conf" doesn't throw error
> ----------------------------------------------------------
>
> Key: HADOOP-9582
> URL: https://issues.apache.org/jira/browse/HADOOP-9582
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 3.0.0, 0.23.7, 2.0.4-alpha
> Reporter: Ashwin Shankar
> Assignee: Ashwin Shankar
> Attachments: HADOOP-9582-4-b23.txt, HADOOP-9582-4.txt,
> HADOOP-9582.txt, HADOOP-9582.txt, HADOOP-9582.txt
>
>
> When we run :
> hadoop fs -conf BAD_FILE -ls /
> we expect hadoop to throw an error,but it doesn't.
--
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
