ci: Add Cannon STF verify recurring job #12165
Merged
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.
This patch adds a recurring CI job that compares the generated states and execution of cannon against an older cannon release. It's an sanity check, over the existing VM tests, asserting that the Cannon STF isn't altered. This can be more robust than existing tests in the VM as it avoids bugs introduced to the test themselves.
For now, the job asserts that changes to Cannon does not alter the state transition function of the singlethreaded V1 state version (i.e. the version used for the Granite upgrade). In the future, the new job will be extended to verify multithreaded cannon and the upcoming cannon STF changes for holocene.