[
https://issues.apache.org/jira/browse/GEODE-7995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Barrett updated GEODE-7995:
---------------------------------
Description:
Concurrency tests tend to use lots of CPU for longer periods of time to test
out concurrency timing issues. They have an impact on the runtime and stability
of other tests in the integration tests when executed in parallel. Concurrency
tests should, perhaps ironically, not be executed in parallel so that each test
gets all the CPU.
CI job should use:
{{no format}}
./gradlew compileConcurrencyTest && ./gradlew concurrencyTest --no-parallel
{{no format}}
was:Concurrency tests tend to use lots of CPU for longer periods of time to
test out concurrency timing issues. They have an impact on the runtime and
stability of other tests in the integration tests when executed in parallel.
Concurrency tests should, perhaps ironically, not be executed in parallel so
that each test gets all the CPU.
> Split out concurrency tests from integration tests.
> ---------------------------------------------------
>
> Key: GEODE-7995
> URL: https://issues.apache.org/jira/browse/GEODE-7995
> Project: Geode
> Issue Type: Improvement
> Components: tests
> Reporter: Jacob Barrett
> Priority: Major
>
> Concurrency tests tend to use lots of CPU for longer periods of time to test
> out concurrency timing issues. They have an impact on the runtime and
> stability of other tests in the integration tests when executed in parallel.
> Concurrency tests should, perhaps ironically, not be executed in parallel so
> that each test gets all the CPU.
> CI job should use:
> {{no format}}
> ./gradlew compileConcurrencyTest && ./gradlew concurrencyTest --no-parallel
> {{no format}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
