Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[TEST-FAILURE] EntryProcessorBouncingNodesTest.testEntryProcessorWhile2NodesAreBouncing #3530

Closed
bilalyasar opened this issue Sep 9, 2014 · 1 comment
Closed

[TEST-FAILURE] EntryProcessorBouncingNodesTest.testEntryProcessorWhile2NodesAreBouncing #3530

bilalyasar opened this issue Sep 9, 2014 · 1 comment
Labels
Source: Internal PR or issue was opened by an employee Type: Test-Failure
Milestone
3.3.1

Comments

@bilalyasar
Copy link
Contributor

https://hazelcast-l337.ci.cloudbees.com/job/Hazelcast-3.x/com.hazelcast$hazelcast/1696/testReport/junit/com.hazelcast.map/EntryProcessorBouncingNodesTest/testEntryProcessorWhile2NodesAreBouncing/

java.lang.AssertionError: CountDownLatch failed to complete within 120 seconds , count left: 1
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.assertTrue(Assert.java:41)
    at com.hazelcast.test.HazelcastTestSupport.assertOpenEventually(HazelcastTestSupport.java:179)
    at com.hazelcast.test.HazelcastTestSupport.assertOpenEventually(HazelcastTestSupport.java:172)
    at com.hazelcast.test.HazelcastTestSupport.assertOpenEventually(HazelcastTestSupport.java:164)
    at com.hazelcast.map.EntryProcessorBouncingNodesTest.testEntryProcessorWhile2NodesAreBouncing(EntryProcessorBouncingNodesTest.java:127)
@bilalyasar bilalyasar added this to the 3.3.1 milestone Sep 9, 2014
@enesakar
Copy link
Contributor

enesakar commented Sep 9, 2014

duplicate #3220

@enesakar enesakar closed this as completed Sep 9, 2014
@mmedenjak mmedenjak added the Source: Internal PR or issue was opened by an employee label Aug 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Source: Internal PR or issue was opened by an employee Type: Test-Failure
Projects
None yet
Milestone
3.3.1
Development

No branches or pull requests
4 participants
@enesakar @Donnerbart @bilalyasar @mmedenjak