[
https://issues.apache.org/jira/browse/GEODE-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-4239:
-----------------------------
Description:
These tests all duplicate the same pattern of using a ExecutorService to
provide a thread that can be deadlocked or live-locked for a concurrency bug:
* DLockServiceLeakTest
* GMSEncryptJUnitTest
* InterruptDiskJUnitTest
* RegionVersionVectorTest
* BlockingProcessStreamReaderWindowsTest
* FileProcessControllerIntegrationTest
* AbortableTaskServiceJUnitTest
* MainLauncherJUnitTest
I'd like to refactor the above list of tests to use a JUnit Rule for this.
was:
These tests all duplicate the same pattern of using a ServiceExecutor to
provide a thread that can be deadlocked or live-locked for a concurrency bug:
* DLockServiceLeakTest
* GMSEncryptJUnitTest
* InterruptDiskJUnitTest
* RegionVersionVectorTest
* BlockingProcessStreamReaderWindowsTest
* FileProcessControllerIntegrationTest
* AbortableTaskServiceJUnitTest
* MainLauncherJUnitTest
I'd like to refactor the above list of tests to use a JUnit Rule for this.
> Create JUnit Rule to facilitate reuse of ExecutorService pattern for
> concurrent integration tests
> -------------------------------------------------------------------------------------------------
>
> Key: GEODE-4239
> URL: https://issues.apache.org/jira/browse/GEODE-4239
> Project: Geode
> Issue Type: Test
> Components: tests
> Reporter: Kirk Lund
> Assignee: Kirk Lund
>
> These tests all duplicate the same pattern of using a ExecutorService to
> provide a thread that can be deadlocked or live-locked for a concurrency bug:
> * DLockServiceLeakTest
> * GMSEncryptJUnitTest
> * InterruptDiskJUnitTest
> * RegionVersionVectorTest
> * BlockingProcessStreamReaderWindowsTest
> * FileProcessControllerIntegrationTest
> * AbortableTaskServiceJUnitTest
> * MainLauncherJUnitTest
> I'd like to refactor the above list of tests to use a JUnit Rule for this.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
