[SERVER-48377] Make MONGO_INITIALIZER scrambling reproducible Created: 21/May/20  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Billy Donahue Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: sa-remove-fv-backlog-22
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-40972 randomize the MONGO_INITIALIZER topol... Closed
Assigned Teams:
Service Arch
Participants:

 Description   

We may have some init-order issues that are showing up as flaky runs, because we randomize the order of mongo initializers, per SERVER-40972.

The initializer order scrambling was done in order to highlight any missing dependency orderings. This may have been successful but without the ability to reproduce the exact order of a failing test, we would probably just call the problem a "flake" and ignore it. We should accept a pseudorandom seed so that failing tests can be re-run.

This could help with test automation and test deflaking, but it could even help with production debugging, since we still do that randomization in production builds.


Generated at Thu Feb 08 05:16:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.