[
https://issues.apache.org/jira/browse/HDFS-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420181#comment-13420181
]
Tomohiko Kinebuchi commented on HDFS-3530:
------------------------------------------
Attached a patch and its intent is described below.
The first error message is "Workload exception 4 testfile /15.dat
java.io.EOFException: Premature EOF: no length prefix available", and after
this moment all other Workload threads failed.
The essential problem on this test failure is unclearness of the objective of
this test case and difficulties to understand what ever happened.
At least we should clear what error case we want to capture, then we are
prepared to implement a test case.
So, I propose to delete this test case.
> TestFileAppend2.testComplexAppend occasionally fails
> ----------------------------------------------------
>
> Key: HDFS-3530
> URL: https://issues.apache.org/jira/browse/HDFS-3530
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Reporter: Eli Collins
> Assignee: Tomohiko Kinebuchi
> Attachments: HDFS-3530-for-debug.txt, PreCommit-HADOOP-Build #1116
> test - testComplexAppend.html.gz
>
>
> TestFileAppend2.testComplexAppend occasionally fails with the following:
> junit.framework.AssertionFailedError: testComplexAppend Worker encountered
> exceptions.
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.assertTrue(Assert.java:20)
> at
> org.apache.hadoop.hdfs.TestFileAppend2.testComplexAppend(TestFileAppend2.java:385)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
