[
https://issues.apache.org/jira/browse/HDFS-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250803#comment-13250803
]
Todd Lipcon commented on HDFS-3243:
-----------------------------------
Seems like this test was lengthened by HDFS-2834. I'm not sure yet whether it
represents a performance regression, or if the test itself was just changed in
such a way that it runs much longer.
On branch-2:
{code}
<testcase time="9.15" classname="org.apache.hadoop.hdfs.TestParallelRead"
name="testParallelRead"/>
{code}
On trunk:
{code}
<testcase time="23.397" classname="org.apache.hadoop.hdfs.TestParallelRead"
name="testParallelReadCopying"/>
<testcase time="133.218" classname="org.apache.hadoop.hdfs.TestParallelRead"
name="testParallelReadByteBuffer"/>
<testcase time="61.364" classname="org.apache.hadoop.hdfs.TestParallelRead"
name="testParallelReadMixed"/>
{code}
I also see a lot of blocked threads in the jstack on trunk. I asked Henry to
take a look at this.
> TestParallelRead timing out on jenkins
> --------------------------------------
>
> Key: HDFS-3243
> URL: https://issues.apache.org/jira/browse/HDFS-3243
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs client, test
> Reporter: Todd Lipcon
> Assignee: Henry Robinson
>
> Trunk builds have been failing recently due to a TestParallelRead timeout. It
> doesn't report in the Jenkins failure list because surefire handles timeouts
> really poorly.
--
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
