[ 
https://issues.apache.org/jira/browse/GEODE-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dan Smith reopened GEODE-5481:
------------------------------

This is still failing in CI, even after the latest changes. Here are some 
failures from running DistributedTest 300 times

{noformat}
org.apache.geode.security.ClientAuthenticationDUnitTest:  5 failures (98.333% 
success rate)
 |  .testCredentialsForNotifications[110]:  1 failures (99.667% success rate)
 |   |  Failed build 268  at 
https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/268
 |  .testCredentialsForNotifications[140]:  1 failures (99.667% success rate)
 |   |  Failed build 175  at 
https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/175
 |  .testCredentialsForNotifications[100]:  1 failures (99.667% success rate)
 |   |  Failed build 1    at 
https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/1
 |  .testCredentialsForNotifications[130]:  2 failures (99.333% success rate)
 |   |  Failed build 266  at 
https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/266
 |   |  Failed build 156  at 
https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/156

{noformat}

http://staging-files.apachegeode-ci.info/builds/1.8.0-build.2/test-results/distributedTest/1534555831/
{noformat}
org.apache.geode.security.ClientAuthenticationDUnitTest > 
testCredentialsForNotifications[110] FAILED
    org.apache.geode.test.dunit.RMIException: While invoking 
org.apache.geode.security.ClientAuthenticationTestCase$$Lambda$76/2041019239.run
 in VM 3 running on Host 9a5176030edc with 4 VMs with version 110
        at org.apache.geode.test.dunit.VM.invoke(VM.java:443)
        at org.apache.geode.test.dunit.VM.invoke(VM.java:412)
        at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
        at 
org.apache.geode.security.ClientAuthenticationTestCase.doTestCredentialsForNotifications(ClientAuthenticationTestCase.java:607)
        at 
org.apache.geode.security.ClientAuthenticationDUnitTest.testCredentialsForNotifications(ClientAuthenticationDUnitTest.java:99)
        
        Caused by:
        java.lang.AssertionError: Event never occurred after 7000 ms: null
{noformat}

> Flaky test ClientAuthenticationDUnitTest > testCredentialsForNotifications
> --------------------------------------------------------------------------
>
>                 Key: GEODE-5481
>                 URL: https://issues.apache.org/jira/browse/GEODE-5481
>             Project: Geode
>          Issue Type: Bug
>          Components: tests
>    Affects Versions: 1.8.0
>            Reporter: Jacob S. Barrett
>            Priority: Major
>              Labels: flaky, swat
>
> org.apache.geode.security.ClientAuthenticationDUnitTest > 
> testCredentialsForNotifications[1] FAILED
>     org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.security.ClientAuthenticationTestCase$$Lambda$76/541487140.run
>  in VM 3 running on Host a41992eb774d with 4 VMs with version 100
>         at org.apache.geode.test.dunit.VM.invoke(VM.java:443)
>         at org.apache.geode.test.dunit.VM.invoke(VM.java:412)
>         at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
>         at 
> org.apache.geode.security.ClientAuthenticationTestCase.doTestCredentialsForNotifications(ClientAuthenticationTestCase.java:647)
>         at 
> org.apache.geode.security.ClientAuthenticationDUnitTest.testCredentialsForNotifications(ClientAuthenticationDUnitTest.java:99)
>         Caused by:
>         java.lang.AssertionError: Event never occurred after 7000 ms: null
> See failed: 
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/152#L5b59cf6d:8141
> See passed: 
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/151#L5b4cf768:9211



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

Reply via email to