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

ClientXAStressTest.testCommitConcurrently #7709

Closed
hasancelik opened this issue Mar 9, 2016 · 1 comment

Comments

Projects
None yet
3 participants
@hasancelik
Copy link
Contributor

commented Mar 9, 2016

java.lang.AssertionError: the size of the map is not correct expected:<10000> but was:<9999>
    at org.junit.Assert.fail(Assert.java:88)
    at org.junit.Assert.failNotEquals(Assert.java:834)
    at org.junit.Assert.assertEquals(Assert.java:645)
    at com.hazelcast.test.HazelcastTestSupport$7.run(HazelcastTestSupport.java:669)
    at com.hazelcast.test.HazelcastTestSupport.assertTrueEventually(HazelcastTestSupport.java:851)
    at com.hazelcast.test.HazelcastTestSupport.assertSizeEventually(HazelcastTestSupport.java:666)
    at com.hazelcast.test.HazelcastTestSupport.assertSizeEventually(HazelcastTestSupport.java:662)
    at com.hazelcast.client.txn.ClientXAStressTest.testCommitConcurrently(ClientXAStressTest.java:82)

https://hazelcast-l337.ci.cloudbees.com/view/Official%20Builds/job/Hazelcast-3.x-nightly/com.hazelcast$hazelcast-client/886/testReport/junit/com.hazelcast.client.txn/ClientXAStressTest/testCommitConcurrently/

https://hazelcast-l337.ci.cloudbees.com/view/Official%20Builds/job/Hazelcast-3.maintenance-nightly/com.hazelcast$hazelcast-client/786/testReport/junit/com.hazelcast.client.txn/ClientXAStressTest/testCommitConcurrently/

@hasancelik

This comment has been minimized.

Copy link
Contributor Author

commented Mar 9, 2016

suppressed by 485f426 & 71f121a

@gurbuzali gurbuzali self-assigned this Mar 9, 2016

@hasancelik hasancelik assigned sancar and unassigned gurbuzali Mar 10, 2016

sancar added a commit to sancar/hazelcast that referenced this issue Mar 11, 2016

Follow up to fix for non blocking Authentication in clients
Original fix was hazelcast#7673 for master, hazelcast#7674 for maintenance-3.x

Recent test failures revealed that some corner cases for that
implementation was missing. One obvious case is if getOrConnect
don't trigger a ConnectTask its Callback is not registered. And
it waits on that callback which will never be called.

fixes hazelcast#7718
fixes hazelcast#7709
fixes hazelcast#7963

sancar added a commit to sancar/hazelcast that referenced this issue Mar 11, 2016

Follow up to fix for non blocking Authentication in clients
Original fix was hazelcast#7673 for master, hazelcast#7674 for maintenance-3.x

Recent test failures revealed that some corner cases for that
implementation was missing. One obvious case is if getOrConnect
don't trigger a ConnectTask its Callback is not registered. And
it waits on that callback which will never be called.

fixes hazelcast#7718
fixes hazelcast#7709
fixes hazelcast#7693

sancar added a commit to sancar/hazelcast that referenced this issue Mar 11, 2016

Follow up to fix for non blocking Authentication in clients
Original fix was hazelcast#7673 for master, hazelcast#7674 for maintenance-3.x

Recent test failures revealed that some corner cases for that
implementation was missing. One obvious case is if getOrConnect
don't trigger a ConnectTask its Callback is not registered. And
it waits on that callback which will never be called.

fixes hazelcast#7718
fixes hazelcast#7709
fixes hazelcast#7693

sancar added a commit to sancar/hazelcast that referenced this issue Mar 11, 2016

Follow up to fix for non blocking Authentication in clients
Original fix was hazelcast#7673 for master, hazelcast#7674 for maintenance-3.x

Recent test failures revealed that some corner cases for that
implementation was missing. One obvious case is if getOrConnect
don't trigger a ConnectTask its Callback is not registered. And
it waits on that callback which will never be called.

fixes hazelcast#7718
fixes hazelcast#7709
fixes hazelcast#7693

sancar added a commit to sancar/hazelcast that referenced this issue Mar 11, 2016

Follow up to fix for non blocking Authentication in clients
Original fix was hazelcast#7673 for master, hazelcast#7674 for maintenance-3.x

Recent test failures revealed that some corner cases for that
implementation was missing. One obvious case is if getOrConnect
don't trigger a ConnectTask its Callback is not registered. And
it waits on that callback which will never be called.

fixes hazelcast#7718
fixes hazelcast#7709
fixes hazelcast#7693

@sancar sancar closed this in #7725 Mar 14, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.