[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:

        // Only run on storage engine's that support snapshot reads.
        if (!_opCtx->getServiceContext()->getStorageEngine()->supportsReadConcernSnapshot()) {
            return;
        }

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: SERVER-35555 StorageTimestampTests dbtest should be run on any storage engine that supports snapshot reads
Branch: master
https://github.com/mongodb/mongo/commit/05e9267ef41f99cf61cdf1e745810580846e567f

Comment by Githook User [ 21/Jun/18 ]

Author:

{'username': 'benety', 'name': 'Benety Goh', 'email': 'benety@mongodb.com'}

Message: SERVER-35555 move logic for skipping test suite from individual tests to setup code for suite
Branch: master
https://github.com/mongodb/mongo/commit/b534ef9f486a72ad2a560ed3ec8b6b1d3a54399a

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