[ 
https://issues.apache.org/jira/browse/GEODE-8266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17316411#comment-17316411
 ] 

Geode Integration commented on GEODE-8266:
------------------------------------------

Seen in [WindowsUnitTestOpenJDK11 
#129|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/129]
 ... see [test 
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0121/test-results/test/1617747975/]
 or download 
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0121/test-artifacts/1617747975/windows-unittestfiles-OpenJDK11-1.15.0-build.0121.tgz].

> StatForNotQueuedConflated not incremented in time
> -------------------------------------------------
>
>                 Key: GEODE-8266
>                 URL: https://issues.apache.org/jira/browse/GEODE-8266
>             Project: Geode
>          Issue Type: Bug
>          Components: wan
>            Reporter: Bill Burcham
>            Priority: Major
>
> Failed here: 
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/259#A
> {code}
> org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderQueueJUnitTest
>  > 
> whenNullPeekedEventFromBucketRegionQueueTheStatForNotQueuedConflatedShouldBeIncremented
>  FAILED
>     java.lang.AssertionError: expected:<1> but was:<0>
>         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 org.junit.Assert.assertEquals(Assert.java:631)
>         at 
> org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderQueueJUnitTest.whenNullPeekedEventFromBucketRegionQueueTheStatForNotQueuedConflatedShouldBeIncremented(ParallelGatewaySenderQueueJUnitTest.java:146)
> {code}
> It appears we are waiting 100ms for the statistic to be incremented. Perhaps 
> we need to wait longer. Or maybe there is product bug here?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to