[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: |
|
||||||||
| 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 |
| Comments |
| Comment by Githook User [ 15/Aug/19 ] |
|
Author: {'username': 'pvselvan', 'email': 'pvselvan@umich.edu', 'name': 'Pavi Vetriselvan'}Message: |
| 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. |