Donal Evans created GEODE-9571:
----------------------------------
Summary: Radish REMRANGE* DUnit tests may fail in stress-test
Key: GEODE-9571
URL: https://issues.apache.org/jira/browse/GEODE-9571
Project: Geode
Issue Type: Bug
Components: redis
Affects Versions: 1.15.0
Reporter: Donal Evans
Failures were seen in pre-checkin stress-new-test for
ZRemRangeByScoreDUnitTest, ZRemRangeByRankDUnitTest and
ZRemRangeByLexDUnitTest, all of which use similar test methods. The failures
were seen in the *RemovesMembersFromSortedSetAfterPrimaryShutsDown() test and
the *CanRemoveMembersFromSortedSetWhenPrimaryIsCrashed() test in a few
different runs.
The failures in *CanRemoveMembersFromSortedSetWhenPrimaryIsCrashed() were seen
when the tests for both ZRemRangeByScoreDUnitTest and ZRemRangeByRankDUnitTest
were being run at the same time due to both classes being changed. It's
possibly relevant that the difference in the second assertion
(expected:<[999]L> but was:<[498]L>) is exactly the incorrect number of members
removed in the first assertion (expected:<[499]L> but was:<[501]L>):
{noformat}
org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest >
zRemRangeByScoreCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed FAILED
java.util.concurrent.ExecutionException: org.junit.ComparisonFailure:
expected:<[499]L> but was:<[501]L>
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at
org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.zRemRangeByScoreCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed(ZRemRangeByScoreDUnitTest.java:159)
Caused by:
org.junit.ComparisonFailure: expected:<[499]L> but was:<[501]L>
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.removeAllButFirstEntry(ZRemRangeByScoreDUnitTest.java:213)
org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest >
zRemRangeByRankCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed FAILED
java.util.concurrent.ExecutionException: org.junit.ComparisonFailure:
expected:<[999]L> but was:<[498]L>
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at
org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest.zRemRangeByRankCanRemoveMembersFromSortedSetWhenPrimaryIsCrashed(ZRemRangeByRankDUnitTest.java:144)
Caused by:
org.junit.ComparisonFailure: expected:<[999]L> but was:<[498]L>
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByRankDUnitTest.removeAllButFirstEntry(ZRemRangeByRankDUnitTest.java:206)
{noformat}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6803/test-results/repeatTest/1630442126/]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
[http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6803/test-artifacts/1630442126/stressnewtestfiles-geode-pr-6803.tgz]
The same failure was also seen in this second run, along with a failure in
ZRemRangeByScoreDUnitTest >
zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown due to the
remove command not finding any members to remove:
{noformat}
org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest >
zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown FAILED
org.junit.ComparisonFailure: expected:<[50]0L> but was:<[]0L>
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.zRemRangeByScoreWithRetries(ZRemRangeByScoreDUnitTest.java:252)
at
org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.doZRemRangeByScoreWithRetries(ZRemRangeByScoreDUnitTest.java:236)
at
org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByScoreDUnitTest.zRemRangeByScoreRemovesMembersFromSortedSetAfterPrimaryShutsDown(ZRemRangeByScoreDUnitTest.java:137)
{noformat}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6803/test-results/repeatTest/1630354947/]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
[http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6803/test-artifacts/1630354947/stressnewtestfiles-geode-pr-6803.tgz]
Finally, a failure in ZRemRangeByLexDUnitTest >
zRemRangeByLexRemovesMembersFromSortedSetAfterPrimaryShutsDown due to the
remove command not finding any members to remove:
{noformat}
org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByLexDUnitTest >
zRemRangeByLexRemovesMembersFromSortedSetAfterPrimaryShutsDown FAILED
org.junit.ComparisonFailure: expected:<[50]0L> but was:<[]0L>
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByLexDUnitTest.zRemRangeByLexWithRetries(ZRemRangeByLexDUnitTest.java:237)
at
org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByLexDUnitTest.doZRemRangeByLexWithRetries(ZRemRangeByLexDUnitTest.java:222)
at
org.apache.geode.redis.internal.executor.sortedset.ZRemRangeByLexDUnitTest.zRemRangeByLexRemovesMembersFromSortedSetAfterPrimaryShutsDown(ZRemRangeByLexDUnitTest.java:138)
{noformat}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6773/test-results/repeatTest/1630456688/]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
[http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6773/test-artifacts/1630456688/stressnewtestfiles-geode-pr-6773.tgz]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)