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

ASF subversion and git services commented on GEODE-3820:
--------------------------------------------------------

Commit e47df106431c693a0b704e1364627a61d875ba66 in geode's branch 
refs/heads/feature/GEODE-4624 from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e47df10 ]

GEODE-3820 CI failure: 
DataSerializerPropogationDUnitTest.testDataSerializersEventIdVerification

This was actually fixed in 5fe3c76d6b1a595c250d924d0115e20f2491cd2a but the
flakytest categorization wasn't removed from the test.  I also added a bounce()
of one of the VMs in a test that would fail if the test is accidentally run
multiple times.


> CI failure: 
> DataSerializerPropogationDUnitTest.testDataSerializersEventIdVerification
> -------------------------------------------------------------------------------------
>
>                 Key: GEODE-3820
>                 URL: https://issues.apache.org/jira/browse/GEODE-3820
>             Project: Geode
>          Issue Type: Bug
>          Components: serialization
>            Reporter: Bruce Schuchardt
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.6.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> This test contains many pauses & needs to be converted to use Awaitility.
> The spelling of this class name should also be corrected.
> org.apache.geode.internal.cache.tier.sockets.DataSerializerPropogationDUnitTest
>  > testDataSerializersEventIdVerificationClientsAndServers FAILED
>     java.lang.AssertionError: EventId found Different
>         at org.junit.Assert.fail(Assert.java:88)
>         at org.junit.Assert.assertTrue(Assert.java:41)
>         at 
> org.apache.geode.internal.cache.tier.sockets.DataSerializerPropogationDUnitTest.testDataSerializersEventIdVerificationClientsAndServers(DataSerializerPropogationDUnitTest.java:673)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to