[GEODE-10190] Improve runtime of some Redis integration tests

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.15.0
• Component/s: redis
• Labels: pull-request-available
• Assignee: Jens Deppe
• Reporter: Jens Deppe
• Created: 29/Mar/22 13:10
• Updated: 22/Jun/22 20:46
• Resolved: 30/Mar/22 02:58

Description

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?

 

 

Issue Links

• links to: GitHub Pull Request #7511