Repository navigation
ci: smart contracts in the robustness suite - #69
Merged
Merged
Conversation
… packet loss, pruning and conversion - run.sh: a SIGKILLed node's executor JVM is killed too (crash test and power cut), or it keeps the port its successor needs; a power cut with contracts waits for the first calls; the calls after go once the restarted nodes and the network after a power cut are 30 blocks past it and the lowest node reached CONTRACTS_AFTER_AT (also without a restart test); the states are compared once every node, a joining one too, reached TARGET_SEQ (contracts-final), bounded by the run's deadline; an executor that could not bind its port fails the run. - contracts.py: --check-nodes (a joining node is compared too), --final-file, and a transaction n1 refuses as not synchronized is sent again for up to 120 s. - .github/actions/contract-executor: the release executor and JDK, shared by testnet.yml and robustness.yml. - robustness.yml: contracts-crash, contracts-power-cut, contracts-net-loss, contracts-pruned-term-kill, contracts-pruned-join, contracts-db-convert. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…tracts-robustness
EnzinoBB
added a commit
that referenced
this pull request
Oct 22, 2026
…tracts-robustness
…f their own after the target Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…tracts-robustness
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.
Step 2 of the plan for testing smart contracts and sizing the test machine. It builds on #68; the base will become
masteronce #68 is merged.run.shA SIGKILLed node no longer leaves its executor JVM running, in the crash test and in the power cut. Before, the orphan kept the port its successor needed.
With contracts, the power cut waits for the first contract calls.
The calls after the restart start only when both are true:
CONTRACTS_AFTER_AT.This now also works without a restart test.
Contract states are compared once every node has reached
TARGET_SEQ, including a node that joined later. The wait is bounded by the run's deadline.An executor that cannot bind its port fails the run.
contracts.py--check-nodesand--final-file..github/actions/contract-executortestnet.ymlandrobustness.yml.New robustness scenarios
contracts-crashcontracts-power-cutcontracts-net-losscontracts-pruned-term-killcontracts-pruned-joincontracts-db-convertScenarios that never kill n1 are the only ones paired with contracts, because
contracts.pysends everything through n1.Validation
rocksdb-crashandmixed-power-cut, to check that nothing changes without contracts.contracts=1at 7 nodes.🤖 Generated with Claude Code