starknet_os_flow_tests: fuzz test call/libcall bad entrypoint scenario#13152
Conversation
This was referenced Mar 10, 2026
|
This change is |
This was referenced Mar 10, 2026
dorimedini-starkware
force-pushed
the
03-08-starknet_os_flow_tests_add_revert_reason_verification_to_fuzz_tests
branch
from
0347dc2 to
9f8cbc9
Compare
dorimedini-starkware
force-pushed
the
03-08-starknet_os_flow_tests_fuzz_test_call_libcall_bad_entrypoint_scenario
branch
from
7cc2ea1 to
0b51682
Compare
|
Artifacts upload workflows: |
This was referenced Mar 11, 2026
Collaborator
Author
This was referenced Mar 11, 2026
dorimedini-starkware
force-pushed
the
03-08-starknet_os_flow_tests_fuzz_test_call_libcall_bad_entrypoint_scenario
branch
from
0b51682 to
989ba5f
Compare
dorimedini-starkware
force-pushed
the
03-08-starknet_os_flow_tests_add_revert_reason_verification_to_fuzz_tests
branch
from
9f8cbc9 to
ae02a02
Compare
dorimedini-starkware
force-pushed
the
03-08-starknet_os_flow_tests_add_revert_reason_verification_to_fuzz_tests
branch
from
ae02a02 to
236e9b0
Compare
dorimedini-starkware
force-pushed
the
03-08-starknet_os_flow_tests_fuzz_test_call_libcall_bad_entrypoint_scenario
branch
from
989ba5f to
030cdca
Compare
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
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.
Note
Medium Risk
Extends fuzz-flow test logic and its on-chain helper contracts to model missing-entrypoint failures, which may change expected revert propagation and test determinism across Cairo0/1.
Overview
Adds two new fuzz scenarios to exercise
call_contract/library_callto a non-existent entry point and validate how those immediate syscall failures propagate (unwrap vs catch) across Cairo0 and Cairo1 contexts.Updates the Cairo0/Cairo1 fuzz contracts and orchestrator to carry new scenario IDs and panic-message plumbing (including a Cairo1 helper
handle_syscall_immediate_failure), and refreshes the Cairo0 compiled artifact and expected class hashes/initial addresses accordingly.Enhances
starknet_os_flow_tests’ Rust-side scenario generator/simulator to emit these operations, synthesize the expectedENTRYPOINT_NOT_FOUNDrevert reason, and pretty-print the new operation types; also adds acairo-lang-runnerdev-dependency for short-string decoding.Written by Cursor Bugbot for commit 030cdca. This will update automatically on new commits. Configure here.