[SERVER-75538] Standardize "sharding_continuous_config_stepdown" suite name to prevent debugging delays Created: 31/Mar/23  Updated: 29/Oct/23  Resolved: 28/Apr/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Pol Pinol Assignee: Pol Pinol
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-05-01
Participants:

 Description   

There is a mismatching suite's names between evergreen and codebase. The name of the suite in evergreen is sharding_csrs_continuous_config_stepdown and in the codebase sharding_continuous_config_stepdown. This type of mismatching often causes us to lose time on finding suite's names and  debugging BFs in evergreen.

The goal of this ticket is to rename either the name in evergreen or the name in the code base.



 Comments   
Comment by Githook User [ 28/Apr/23 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-75538 Standardize "sharding_continuous_config_stepdown" suite name to prevent debugging delays
Branch: master
https://github.com/mongodb/mongo/commit/2b0786a775d688b049686721dd172bd4b4a053a5

Generated at Thu Feb 08 06:30:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.