You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/09/29 19:48:00 UTC

[jira] [Commented] (GEODE-7995) Split out concurrency tests from integration tests.

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

ASF GitHub Bot commented on GEODE-7995:
---------------------------------------

onichols-pivotal commented on pull request #4969:
URL: https://github.com/apache/geode/pull/4969#issuecomment-700946918


   closed due to lack of activity


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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
>              Labels: pull-request-available
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> 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:
> {code:java}
> ./gradlew compileConcurrencyTest && ./gradlew concurrencyTest --no-parallel
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)