ci: add daily rln simulator e2e workflow#3885
Open
darshankabariya wants to merge 7 commits into
Open
Conversation
|
You can find the image built from this PR at Built from 6a1925c |
darshankabariya
requested review from
Ivansete-status,
NagyZoltanPeter and
fcecin
7 tasks
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
1 participant
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.
We're moving logos delivery to the logos-dev fleet, where RLN is disabled — so no production traffic exercises RLN anymore. Proof generation, on-chain registration, rate limiting, and epoch recovery can silently regress with nothing to catch it until RLN is re-enabled there.
This PR automates that as a daily safety net: build wakunode2 on the runner, run logos-delivery-simulator, and assert the full RLN flow (keystore → on-chain register → gossipsub propagation → per-epoch rate limit → epoch recovery).