[
https://issues.apache.org/jira/browse/HDFS-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932308#action_12932308
]
Todd Lipcon commented on HDFS-1500:
-----------------------------------
Apologies about not calling that out, Jakob.
The fail() statements were actually counterproductive as I was debugging the
test. The issue is that appending exception.toString() ends up obscuring the
stack trace of any failure. Without the catch/fail, you can still always see
which function the exception came from, so you don't lose anything.
> TestOfflineImageViewer failing on trunk
> ---------------------------------------
>
> Key: HDFS-1500
> URL: https://issues.apache.org/jira/browse/HDFS-1500
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test, tools
> Affects Versions: 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hdfs-1500.txt
>
>
> Testcase: testOIV took 22.679 sec
> FAILED
> Failed reading valid file: No image processor to read version -26 is
> available.
> junit.framework.AssertionFailedError: Failed reading valid file: No image
> processor to read version -26 is available.
> at
> org.apache.hadoop.hdfs.tools.offlineImageViewer.TestOfflineImageViewer.outputOfLSVisitor(TestOfflineImageViewer.java:171)
> at
> org.apache.hadoop.hdfs.tools.offlineImageViewer.TestOfflineImageViewer.testOIV(TestOfflineImageViewer.java:86)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
