[jira] [Commented] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[ https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17407324#comment-17407324 ] ASF subversion and git services commented on GEODE-9252: Commit 38b22dc36a24774187faef90a3ee7dce27e6e51d in geode's branch refs/heads/develop from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=38b22dc ] GEODE-9252: Wait longer for Redis cluster to be formed (#6817) > CI failure: NativeRedisClusterTestRule incorrect primary node count (expected > 3 but was 2) > -- > > Key: GEODE-9252 > URL: https://issues.apache.org/jira/browse/GEODE-9252 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Owen Nichols >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > {noformat} > org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest > > classMethod FAILED > org.junit.ComparisonFailure: [Incorrect primary node count] > expected:<[3]> but was:<[2]> > at > org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93) > {noformat} > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[ https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17406958#comment-17406958 ] Jens Deppe commented on GEODE-9252: --- Agreed - I'll increase it to 60 seconds > CI failure: NativeRedisClusterTestRule incorrect primary node count (expected > 3 but was 2) > -- > > Key: GEODE-9252 > URL: https://issues.apache.org/jira/browse/GEODE-9252 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Owen Nichols >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > {noformat} > org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest > > classMethod FAILED > org.junit.ComparisonFailure: [Incorrect primary node count] > expected:<[3]> but was:<[2]> > at > org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93) > {noformat} > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[ https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404778#comment-17404778 ] Dan Smith commented on GEODE-9252: -- On the face of it, 5 seconds seems like too short of a time to avoid having flaky tests on a CI machine. Maybe we should just up the timeout where we are waiting for primary nodes? > CI failure: NativeRedisClusterTestRule incorrect primary node count (expected > 3 but was 2) > -- > > Key: GEODE-9252 > URL: https://issues.apache.org/jira/browse/GEODE-9252 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Owen Nichols >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > {noformat} > org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest > > classMethod FAILED > org.junit.ComparisonFailure: [Incorrect primary node count] > expected:<[3]> but was:<[2]> > at > org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93) > {noformat} > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[ https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17356584#comment-17356584 ] ASF subversion and git services commented on GEODE-9252: Commit 363d094f2c8e5b22512b026061acb95a843bf4e6 in geode's branch refs/heads/develop from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=363d094 ] GEODE-9252: Improve NativeRedisClusterTestRule waiting for cluster to be ready (#6553) - Seems that waiting for the 'cluster ready' message is not enough, so now loop for up to 5 seconds for all primaries to appear. > CI failure: NativeRedisClusterTestRule incorrect primary node count (expected > 3 but was 2) > -- > > Key: GEODE-9252 > URL: https://issues.apache.org/jira/browse/GEODE-9252 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Owen Nichols >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > {noformat} > org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest > > classMethod FAILED > org.junit.ComparisonFailure: [Incorrect primary node count] > expected:<[3]> but was:<[2]> > at > org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93) > {noformat} > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[ https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355409#comment-17355409 ] Donal Evans commented on GEODE-9252: Seen again in a PR pre-checkin run, [https://concourse.apachegeode-ci.info/builds/44622#L6071513e:312] Results archived below: =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6523/test-results/acceptanceTest/1622590184/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6523/test-artifacts/1622590184/acceptancetestfiles-geode-pr-6523.tgz > CI failure: NativeRedisClusterTestRule incorrect primary node count (expected > 3 but was 2) > -- > > Key: GEODE-9252 > URL: https://issues.apache.org/jira/browse/GEODE-9252 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Owen Nichols >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > {noformat} > org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest > > classMethod FAILED > org.junit.ComparisonFailure: [Incorrect primary node count] > expected:<[3]> but was:<[2]> > at > org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93) > {noformat} > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[ https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17353917#comment-17353917 ] Jens Deppe commented on GEODE-9252: --- Please re-open this ticket if it recurs and please do ping [~jens.deppe] > CI failure: NativeRedisClusterTestRule incorrect primary node count (expected > 3 but was 2) > -- > > Key: GEODE-9252 > URL: https://issues.apache.org/jira/browse/GEODE-9252 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Owen Nichols >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > {noformat} > org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest > > classMethod FAILED > org.junit.ComparisonFailure: [Incorrect primary node count] > expected:<[3]> but was:<[2]> > at > org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93) > {noformat} > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[ https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17353581#comment-17353581 ] Geode Integration commented on GEODE-9252: -- Seen in [acceptance-test-openjdk8 #2|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/2] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0278/test-results/acceptanceTest/1622238627/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0278/test-artifacts/1622238627/acceptancetestfiles-openjdk8-1.15.0-build.0278.tgz]. > CI failure: NativeRedisClusterTestRule incorrect primary node count (expected > 3 but was 2) > -- > > Key: GEODE-9252 > URL: https://issues.apache.org/jira/browse/GEODE-9252 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Owen Nichols >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > {noformat} > org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest > > classMethod FAILED > org.junit.ComparisonFailure: [Incorrect primary node count] > expected:<[3]> but was:<[2]> > at > org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93) > {noformat} > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[ https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17353552#comment-17353552 ] ASF subversion and git services commented on GEODE-9252: Commit d0a63049d2d66c76b6eff8faa1d375b7379ea2d2 in geode's branch refs/heads/develop from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d0a6304 ] GEODE-9252: Improve startup of NativeRedisClusterTestRule (#6538) - Sometimes the docker cluster startup appears to complete but cluster nodes reports fewer than expected primaries. > CI failure: NativeRedisClusterTestRule incorrect primary node count (expected > 3 but was 2) > -- > > Key: GEODE-9252 > URL: https://issues.apache.org/jira/browse/GEODE-9252 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Owen Nichols >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > {noformat} > org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest > > classMethod FAILED > org.junit.ComparisonFailure: [Incorrect primary node count] > expected:<[3]> but was:<[2]> > at > org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93) > {noformat} > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[ https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17353377#comment-17353377 ] Geode Integration commented on GEODE-9252: -- Seen in [acceptance-test-openjdk8 #1|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/1] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0276/test-results/acceptanceTest/1622172653/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0276/test-artifacts/1622172653/acceptancetestfiles-openjdk8-1.15.0-build.0276.tgz]. > CI failure: NativeRedisClusterTestRule incorrect primary node count (expected > 3 but was 2) > -- > > Key: GEODE-9252 > URL: https://issues.apache.org/jira/browse/GEODE-9252 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Owen Nichols >Priority: Major > > {noformat} > org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest > > classMethod FAILED > org.junit.ComparisonFailure: [Incorrect primary node count] > expected:<[3]> but was:<[2]> > at > org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93) > {noformat} > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[ https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17350516#comment-17350516 ] Geode Integration commented on GEODE-9252: -- Seen in [AcceptanceTestOpenJDK11 #231|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK11/builds/231] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0257/test-results/acceptanceTest/1621862107/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0257/test-artifacts/1621862107/acceptancetestfiles-OpenJDK11-1.15.0-build.0257.tgz]. > CI failure: NativeRedisClusterTestRule incorrect primary node count (expected > 3 but was 2) > -- > > Key: GEODE-9252 > URL: https://issues.apache.org/jira/browse/GEODE-9252 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Owen Nichols >Priority: Major > > {noformat} > org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest > > classMethod FAILED > org.junit.ComparisonFailure: [Incorrect primary node count] > expected:<[3]> but was:<[2]> > at > org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93) > {noformat} > -- This message was sent by Atlassian Jira (v8.3.4#803005)