[SERVER-35053] causal consistency passthroughs erroneously blacklist tests Created: 17/May/18  Updated: 29/Oct/23  Resolved: 02/Jul/18

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

Type: Bug Priority: Major - P3
Reporter: Xiangyu Yao (Inactive) Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2018-07-16
Participants:

 Description   

In causally_consistent_jscore_passthrough.yml, a section does not make sense since we don't inject any read/write concern in the suite. We should probably update the blacklist.

# Tests that won't work with an injected 'majority' readConcern               
# and/or an injected 'majority' writeConcern. Where a function is             
# listed the reason is we don't have a reliable solution to override          
# the write concern for that function.           



 Comments   
Comment by Githook User [ 02/Jul/18 ]

Author:

{'username': 'jsmulrow', 'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com'}

Message: SERVER-35053 Remove injected read/write concern blacklists from causal consistency passthroughs
Branch: master
https://github.com/mongodb/mongo/commit/f683298f0f85129b4eaf0c16244fe984943f42ce

Comment by Misha Tyulenev [ 11/Jun/18 ]

causally_consistent_jscore_passthrough.yml does not inject read/writeConcern “majority” but this section is excluding tests that cannot work with “majority” writeConcern

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