feat: NMv3: per kind scheduling - #7095
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The orchestrator can now assign liveness work as well as stress work.
assign_next_mixnode_testrunbecomesassign_next_testruns(&AssignmentRequest), taking aTestPairing(kind + role) and returning a wave. Per-role eligibility adds the node types a role may assign plus the fields its probe needs.TestKind(via strum, so a new kind joins by existing), skipping disabled kinds and falling through when one has nothing due. Within a kind, the pairing whose next node is furthest behind wins, so the two liveness roles interleave by need rather than by a fixed share.This change is