[
https://issues.apache.org/jira/browse/GOSSIP-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668317#comment-15668317
]
Edward Capriolo commented on GOSSIP-18:
---------------------------------------
The issue here has been convergence times. As we added services/executors they
have tended to elongate the shutdown time. Gossip 22 will fix this but for now
I am going to up the worst case test time. 20 seconds is too lean for the worst
case.
> ShutdownDeadtimeTest failure
> -----------------------------
>
> Key: GOSSIP-18
> URL: https://issues.apache.org/jira/browse/GOSSIP-18
> Project: Gossip
> Issue Type: Bug
> Environment: OS: Debian
> kernel: 4.6.0-1-rt-686-pae
> JDK: 1.8.0_73 build 25.73-b02, mixed mode
> maven: 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
> 21:51:28+0800)
> Reporter: ChiaHung Lin
> Assignee: Edward Capriolo
> Priority: Minor
>
> When executing maven, test case ShutdownDeadtimeTest sometimes fails even
> with clean checkout.
> org.junit.ComparisonFailure: ComparisonFailure expected:<[16]> but was:<[2]>
> at
> org.apache.gossip.ShutdownDeadtimeTest.DeadNodesDoNotComeAliveAgain(ShutdownDeadtimeTest.java:100)
> Results :
> Failed tests:
> ShutdownDeadtimeTest.DeadNodesDoNotComeAliveAgain:100
> ComparisonFailure expected:<[16]> but was:<[2]>
> TenNodeThreeSeedTest.testAgain:52->abc:90 ComparisonFailure
> expected:<[2]0> but was:<[]0>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
