[jira] [Updated] (GEODE-5662) Flaky unit test ExecutorServiceRuleTest.threadCountTwoHasTwoThreads

["Dan Smith (JIRA)" <ji...@apache.org>]

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

Dan Smith updated GEODE-5662:
-----------------------------
    Summary: Flaky unit test ExecutorServiceRuleTest.threadCountTwoHasTwoThreads  (was: Flaky unit test ExecutorServiceRuleTest)

> Flaky unit test ExecutorServiceRuleTest.threadCountTwoHasTwoThreads
> -------------------------------------------------------------------
>
>                 Key: GEODE-5662
>                 URL: https://issues.apache.org/jira/browse/GEODE-5662
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Dan Smith
>            Priority: Major
>              Labels: swat
>
> This test failed in CI. To me it looks like this test seems to be assuming that if it schedules two tasks they will actually run concurrently, which may or may not happen depending on timing.
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/Build/builds/403
> {noformat}
> org.apache.geode.test.junit.rules.ExecutorServiceRuleTest > threadCountTwoHasTwoThreads FAILED
>     org.junit.ComparisonFailure: expected:<[2]> but was:<[1]>
>         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>         at org.apache.geode.test.junit.rules.ExecutorServiceRuleTest.threadCountTwoHasTwoThreads(ExecutorServiceRuleTest.java:130)
> {noformat}



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