[SERVER-50861] Fully initialize the ServiceContext for unit tests that depend on the checkpoint thread Created: 10/Sep/20 Updated: 29/Oct/23 Resolved: 04/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | techdebt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2023-04-17 |
| Participants: |
| Description |
|
With the changes being made in
The only unit test depending on checkpoints today that I know of is WiredTigerKVEngineTest::TestOplogTruncation. |
| Comments |
| Comment by Githook User [ 04/Apr/23 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Dianna Hohensee (Inactive) [ 10/Sep/20 ] |
|
I'd recommend trying to pull the WiredTigerKVEngineTest::TestOplogTruncation up to a higher level of unit testing. Now that the checkpointing thread will be above the storage layer, we should have the unit testing at the same level. Then we don't need to change the lower level testing infrastructure. |