[SERVER-34694] mongod_returns_no_cluster_time_without_keys.js should not run with inMemory SE Created: 26/Apr/18  Updated: 29/Oct/23  Resolved: 26/Apr/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
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: Sharding 2018-05-07
Participants:
Linked BF Score: 7

 Description   

This test manually restarts a shard, which should not be done with the inMemory storage engine, since it doesn't persist any data from before the restart. The test only runs one command after the restart, which isn't wrapped in an assert.commandWorked, which is likely the only reason this test doesn't always fail on the inMemory variants.

The test should add the requires_persistence tag to prevent inMemory variants from running it.



 Comments   
Comment by Githook User [ 26/Apr/18 ]

Author:

{'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow', 'name': 'Jack Mulrow'}

Message: SERVER-34694 mongod_returns_no_cluster_time_without_keys.js should not run with inMemory SE
Branch: master
https://github.com/mongodb/mongo/commit/c799c6c67537e0d6f65003c141b444897ad9e408

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