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 2022/03/29 13:22:00 UTC

[jira] [Updated] (GEODE-10190) Improve runtime of some Redis integration tests

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

ASF GitHub Bot updated GEODE-10190:
-----------------------------------
    Labels: pull-request-available  (was: )

> Improve runtime of some Redis integration tests
> -----------------------------------------------
>
>                 Key: GEODE-10190
>                 URL: https://issues.apache.org/jira/browse/GEODE-10190
>             Project: Geode
>          Issue Type: Improvement
>          Components: redis
>            Reporter: Jens Deppe
>            Assignee: Jens Deppe
>            Priority: Major
>              Labels: pull-request-available
>
> From Darrel:
> _I’m doing some refactoring of the ResourceManager and my pr’s integration tests are timing out after running for 45 minutes. Normally integration tests take 18 minutes. When looking at whats tests took a long time I see that AbstractRenameIntegrationTest#shouldRenameAtomically took 8 minutes each time it was run. On my laptop I see it run in 2.75 minutes. Another test method I see take over 7 minutes is testMSet_concurrentInstances_mustBeAtomic. These two methods are run twice so that adds up to 30 minutes in just two test methods so I think that is the cause of the timeout. Both of these do concurrency. Any ideas about this? Do you think my refactoring broke something or did I just get a bad run of these tests?_
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)