[
https://issues.apache.org/jira/browse/GEODE-10190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514415#comment-17514415
]
ASF subversion and git services commented on GEODE-10190:
---------------------------------------------------------
Commit 7c010278dfd8afbbd202d5f541932a8eabbbae26 in geode's branch
refs/heads/develop from Jens Deppe
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7c01027 ]
GEODE-10190: Improve runntime of MSetIntegrationTest and RenameIntegratinoTest
(#7511)
- Reduce the iterations and/or elements used by these tests reducing the
runtimes significantly (down to seconds instead of minutes).
> 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
> Fix For: 1.15.0
>
>
> 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)
