[SERVER-53694] CleanEveryN timing information needs to accounts for hard-coded N Created: 11/Jan/21  Updated: 29/Oct/23  Resolved: 12/Jan/21

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.9.0, 4.4.4

Type: Bug Priority: Major - P3
Reporter: David Bradford (Inactive) Assignee: David Bradford (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: DAG 2021-01-25
Participants:
Linked BF Score: 50
Story Points: 2

 Description   

When considering how time from "CleanEveryN" will impact a task runtime, we need to consider the case where N is hard-coded to one.



 Comments   
Comment by Githook User [ 12/Jan/21 ]

Author:

{'name': 'David Bradford', 'email': 'david.bradford@mongodb.com', 'username': 'dbradf'}

Message: SERVER-53694: Take hard-coded CleanEveryN values into account for timeouts

(cherry picked from commit b6df39916f37f6029dc561f73ab157346982340b)
Branch: v4.4
https://github.com/mongodb/mongo/commit/f2d7070e3b441997353c177d19f10add1c753e5f

Comment by Githook User [ 12/Jan/21 ]

Author:

{'name': 'David Bradford', 'email': 'david.bradford@mongodb.com', 'username': 'dbradf'}

Message: SERVER-53694: Take hard-coded CleanEveryN values into account for timeouts
Branch: master
https://github.com/mongodb/mongo/commit/b6df39916f37f6029dc561f73ab157346982340b

Generated at Thu Feb 08 05:31:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.