[SERVER-22091] Run FSM suites with readConcern/writeConcern overrides Created: 22/Oct/15  Updated: 12/Oct/18  Resolved: 12/Oct/18

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

Type: Improvement Priority: Major - P3
Reporter: Kamran K. Assignee: DO NOT USE - Backlog - Test Infrastructure Group (TIG)
Resolution: Done Votes: 0
Labels: tig-concurrency
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-21450 Modify MongoRunner to add enableMajor... Closed
Related
is related to SERVER-19488 FSM tests - standalone tests invoked ... Closed
is related to SERVER-19630 FSM tests - capability to run against... Closed
Sprint: TIG C (11/20/15), TIG D (12/11/15)
Participants:

 Description   

I'd like to see if we can uncover further bugs by using the FSM sharded replication and FSM replication workloads with the readConcern/writeConcern overrides that are used in the readMajority passthrough.



 Comments   
Comment by Max Hirschhorn [ 12/Oct/18 ]

We're already doing this through the concurrency_sharded_with_stepdowns*.yml test suites.

Generated at Thu Feb 08 03:59:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.