[GEODE-9374] CI Failure: RestoreRedundancyOperationDUnitTest > statsAreUpdatedWhenRestoreRedundancyIsCalled

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.14.0, 1.15.0
• Fix Version/s: 1.14.0, 1.15.0
• Labels: blocks-1.14.0​ flaky pull-request-available
• Assignee: Donal Evans
• Reporter: Donal Evans
• Created: 11/Jun/21 22:38
• Updated: 03/Sep/21 02:21
• Resolved: 07/Jul/21 16:31

Description

org.apache.geode.internal.cache.control.RestoreRedundancyOperationDUnitTest > statsAreUpdatedWhenRestoreRedundancyIsCalled FAILED
 org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.control.RestoreRedundancyOperationDUnitTest$$Lambda$87/347190495.run in VM 1 running on Host 72dc24287840 with 4 VMs
 at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
 at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
 at org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
 at org.apache.geode.internal.cache.control.RestoreRedundancyOperationDUnitTest.statsAreUpdatedWhenRestoreRedundancyIsCalled(RestoreRedundancyOperationDUnitTest.java:108)

Caused by:
 java.lang.AssertionError: 
 Expected: <0L>
 but: was <1L>
 at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
 at org.junit.Assert.assertThat(Assert.java:964)
 at org.junit.Assert.assertThat(Assert.java:930)
 at org.apache.geode.internal.cache.control.RestoreRedundancyOperationDUnitTest.lambda$statsAreUpdatedWhenRestoreRedundancyIsCalled$bb17a952$1(RestoreRedundancyOperationDUnitTest.java:114)

=============== Test Results URI =================
http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0759/test-results/distributedTest/1618882514/
=========================================

Test report artifacts from this job are available at:

http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0759/test-artifacts/1618882514/distributedtestfiles-OpenJDK8-1.14.0-build.0759.tgz

Seen in the support/1.14 pipeline. This test has never been reported to fail before, so this is likely a flaky failure that could be fixed by using an await() for the stat to have the expected value.

Issue Links

• links to: GitHub Pull Request #6649
• links to: GitHub Pull Request #6678