Separate fullnode & supernode devnet checkpoint sync into two separate jobs #8238
Conversation
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
…e jobs, as the runner was struggling with supernode syncing.
|
Maybe also need to modify the I see that the supernode has completed the backfill, but the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue Addressed
The supernode checkpoint sync test was failing to backfill, it seems like the blob count on devnet-3 may be too high for a github hosted runner to run both a supernode and a fullnode.
Separating it into a separate test to see if it passes. Devnet-3 is probably going to be removed soon but I think it's worth try this out as we may want to test supernode sync on sepolia.