vopr: scenario + workload synthesis layers - #58
Merged
Conversation
oreofeolurin
force-pushed
the
feat/vopr-simulation-testing
branch
from
August 29, 2026 22:30
76b3fd6 to
6cc6839
Compare
First slice of FLO-107: seed-deterministic swarm scenario synthesis and self-verifying workload generation with the op oracle. Payload/ring sampling is constrained so an AppendEntries batch can never evict its own head; deliberately-small rings live behind Scenario.smallRing for the watchdog-wrapped slice. The simulator that consumes these lands with FLO-119.
oreofeolurin
force-pushed
the
feat/vopr-simulation-testing
branch
from
August 30, 2026 14:55
6cc6839 to
770e840
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
First slice of the FloVOPR simulation-testing framework:
src/vopr/{scenario,workload,mod}.zig— seed-deterministic swarm scenario synthesis (JSON-emitting, replayable via a serialized scenario rather than a bare seed) and self-verifying workload generation with the op oracle.stdx.PRNGexported; module registered in the unit-test root and assrc.vopr.Why
One seed must reproduce an entire cluster run — scenario, faults, every op payload. Payload/ring sampling is constrained so an AppendEntries batch can never evict its own head; deliberately-small rings live behind
Scenario.smallRing.Watch
src.vopr.