[SERVER-39342] The sharding unit-tests' `kFutureTimeout` duration is too short for slow variants Created: 01/Feb/19  Updated: 29/Oct/23  Resolved: 04/Feb/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.1.8

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2019-02-11
Participants:
Linked BF Score: 18

 Description   

The sharding unit-tests, which spawn asynchronous activities via launchAsync wait for up to kFutureTimeout = 5 seconds for these activities to complete. Some of these tasks however may perform database writes and other storage engine operations and on slower variants, such as DEBUG on arm64, this may take more than 5 seconds.

In order to make these tests more robust on slower variants we should increase this constant to 15 seconds.



 Comments   
Comment by Githook User [ 04/Feb/19 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-39342 Bump the sharding unit-tests' `kFutureTimeout` constant to 15 seconds
Branch: master
https://github.com/mongodb/mongo/commit/95c5d57d8a3f613ba79ef83a0390a8ba9bc8fc40

Generated at Thu Feb 08 04:51:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.