[SERVER-70339] Sharding tests combination Created: 07/Oct/22  Updated: 29/Oct/23  Resolved: 13/Feb/23

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

Type: Improvement Priority: Major - P3
Reporter: Alex Neben Assignee: Trevor Guidry
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   
  • Sharding test suites (35% including "jscore sharding")
  • sharding_max_mirroring
  • sharding_ese
  • sharding_ese_gcm
  • sharding_auth
  • sharding_auth_audit
  • sharding_hello_failures
  • sharding_opportunistic_secondary_targeting

These tests can be combined robert.guo@mongodb.com can you provide a little more context here?



 Comments   
Comment by Trevor Guidry [ 16/Feb/23 ]

The total saving for these changes is ~25k.

Comment by Githook User [ 09/Feb/23 ]

Author:

{'name': 'Trevor Guidry', 'email': 'trevor.guidry@mongodb.com', 'username': ''}

Message: SERVER-70339 aggregate sharding resmoke suites
Branch: master
https://github.com/mongodb/mongo/commit/d9870d028e314c7f7c7261a8138988a7f21b6f07

Comment by Robert Guo (Inactive) [ 07/Oct/22 ]

Per mark.benvenuto@mongodb.com's point in the scope, sharding_ese and sharding_ese_gcm are mutually exclusive. We'll need to keep one and run the other one for one the jscore sharding passthroughs as a part of SERVER-70337. Here's an example of what the ese_gcm option would look like for jscore passthrough.

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