[SERVER-50190] Exclude requires_capped from concurrency tests that use transaction with snapshot Created: 08/Aug/20  Updated: 29/Oct/23  Resolved: 10/Aug/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Bug Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Lingzhi Deng
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2020-08-24
Participants:
Linked BF Score: 50

 Description   

SERVER-47824 banned transaction snapshot reads on capped collections. For concurrency tests that have runInsideTransaction: true, they run with transactions with readConcern snapshot by default unless defaultTransactionReadConcernLevel is specified. So we should exclude the requires_capped tag for those suites.



 Comments   
Comment by Githook User [ 10/Aug/20 ]

Author:

{'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}

Message: SERVER-50190: Exclude requires_capped tag from concurrency_replication_multi_stmt_txn_ubsan.yml
Branch: master
https://github.com/mongodb/mongo/commit/42fbd710722bb0e21297760fc85446a7786244b8

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