[SERVER-35555] Turn on dbtest's StorageTimestampTests for `inMemory` Created: 12/Jun/18 Updated: 29/Oct/23 Resolved: 21/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Storage NYC 2018-07-02 |
| Participants: |
| Description |
|
...And investigate why it doesn't work. Each StorageTimestampTest starts with a block that excludes non-WT storage engines. I believe the code can refer to supporting snapshot reads instead, e.g:
However, a quick check showed Enterprise's inMemory failed the SecondaryInsertTimes test. I didn't try running the others. |
| Comments |
| Comment by Githook User [ 21/Jun/18 ] |
|
Author: {'username': 'benety', 'name': 'Benety Goh', 'email': 'benety@mongodb.com'}Message: |
| Comment by Githook User [ 21/Jun/18 ] |
|
Author: {'username': 'benety', 'name': 'Benety Goh', 'email': 'benety@mongodb.com'}Message: |