[SERVER-41699] Make sure we are running transactions tests with the inMemory storage engine Created: 13/Jun/19  Updated: 29/Oct/23  Resolved: 15/Aug/19

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

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

Issue Links:
Related
is related to SERVER-38165 Test that prepared transactions work ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2019-07-15, Repl 2019-07-29, Repl 2019-08-12, Repl 2019-08-26
Participants:

 Description   

When looking through the evergreen.yml, it seems like a lot of our core_txns tests run with the wiredTiger storage engine only.

We should make sure we test transactions with the inMemory storage engine as well since it looks like we mean for it to run more tests. This was likely meant to be done in SERVER-38165.



 Comments   
Comment by Githook User [ 15/Aug/19 ]

Author:

{'username': 'pvselvan', 'email': 'pvselvan@umich.edu', 'name': 'Pavi Vetriselvan'}

Message: SERVER-41699 enable transactions and initial sync fuzzer in inMemory storage engine
Branch: master
https://github.com/mongodb/mongo/commit/1a39fab6a77a6fdddc889aaffa116b3376bfc488

Comment by Vlad Rachev (Inactive) [ 20/Jun/19 ]

As part of this ticket we should also enable running the initial sync fuzzer against the inMemory storage engine variant.

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