[
https://issues.apache.org/jira/browse/HDFS-9610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15117935#comment-15117935
]
Colin Patrick McCabe commented on HDFS-9610:
--------------------------------------------
This is not a bug. {{test_libhdfs_threaded_hdfs_static}} tests that things
work properly when it tries to access a file that doesn't exist. That's why
you see {{java.io.FileNotFoundException: File does not exist:
/tlhData0001/file1}}.
The error message about an illegal open mode comes from here:
{code}
/* hdfsOpenFile should not accept mode = 3 */
EXPECT_NULL(hdfsOpenFile(fs, paths->file1, 3, 0, 0, 0));
{code}
And so on, and so forth.
We do want to keep those stderr and stdout log messages, since they are needed
to debug actual failures that might happen. Maybe we can add a per-test option
for the pom.xml to suppress stderr output on tests we know are noisy.
This reminds me... Yetus should be keeping the .stderr and .stdout files that
the CMake test plugin generates... I should file a JIRA for that.
> cmake tests don't fail when they should?
> ----------------------------------------
>
> Key: HDFS-9610
> URL: https://issues.apache.org/jira/browse/HDFS-9610
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Reporter: Allen Wittenauer
> Assignee: James Clampffer
> Attachments: HDFS-9610.HDFS-8707.000.patch, LastTest.log
>
>
> Playing around with adding ctest output support to Yetus, and I stumbled upon
> a case where the tests throw errors left and right but claim success.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
