[
https://issues.apache.org/jira/browse/DL-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15800642#comment-15800642
]
Hudson commented on DL-165:
---------------------------
UNSTABLE: Integrated in Jenkins build distributedlog-nightly-build #179 (See
[https://builds.apache.org/job/distributedlog-nightly-build/179/])
DL-165: Add TestTimedOutTestsListener to dump timed out cases thread (sijieg:
rev ea3c1143f9e2718d0d86e8b1c8f3a7e51ac19c4d)
* (add)
distributedlog-protocol/src/test/java/com/twitter/distributedlog/TestTimedOutTestsListener.java
* (edit) distributedlog-protocol/pom.xml
* (edit) distributedlog-core/pom.xml
* (edit) NOTICE
* (edit) distributedlog-client/pom.xml
* (add)
distributedlog-protocol/src/test/java/com/twitter/distributedlog/TimedOutTestsListener.java
* (edit) distributedlog-service/pom.xml
> Add TimedOutTestsListener to print the full thread dump on test timeout
> -----------------------------------------------------------------------
>
> Key: DL-165
> URL: https://issues.apache.org/jira/browse/DL-165
> Project: DistributedLog
> Issue Type: Improvement
> Components: tests
> Affects Versions: 0.4.0
> Reporter: Liang Xie
> Assignee: Liang Xie
> Fix For: 0.4.0
>
>
> The TestBKSyncLogReader.testReadRecordsAfterReadAheadCaughtUp case seems
> failed frequently due to timeout, i.e.
> https://builds.apache.org/job/distributedlog-precommit-pullrequest/com.twitter$distributedlog-core/56/testReport/junit/com.twitter.distributedlog/TestBKSyncLogReader/testReadRecordsAfterReadAheadCaughtUp/
> From the log, it's hard to figure out the root cause, it may be helpful if we
> had the full thread dump. we can add a TimedOutTestsListener just like
> netty/hadoop projects, please refer to :
> https://github.com/junit-team/junit4/issues/463 ,
> https://github.com/netty/netty/pull/4749/files ,
> https://issues.apache.org/jira/browse/HADOOP-8755 for more details
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
