-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test(blockifier): intermediate with_attr error message #630
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main-v0.13.2 #630 +/- ##
================================================
- Coverage 76.46% 71.15% -5.31%
================================================
Files 315 68 -247
Lines 34098 9482 -24616
Branches 34098 9482 -24616
================================================
- Hits 26073 6747 -19326
+ Misses 5763 2325 -3438
+ Partials 2262 410 -1852 ☔ View full report in Codecov by Sentry. |
774ac22
to
8d5adef
Compare
@dorimedini-starkware is there a way to hardcode the variables here? I want to call Code quote: contract_address: felt, function_selector: felt, calldata_len: felt, calldata: felt* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 4 of 4 files at r1, all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @aner-starkware and @TzahiTaub)
crates/blockifier/feature_contracts/cairo0/test_contract.cairo
line 170 at r1 (raw file):
Previously, aner-starkware wrote…
@dorimedini-starkware is there a way to hardcode the variables here? I want to call
call_contract
with the current contract and the functionfail
.
- you shouldn't hard-code the address, it depends on the executing code (to which address is it deployed?)
- selector and calldata - you can probably hard-code, yes
crates/blockifier/src/execution/stack_trace_test.rs
line 116 at r1 (raw file):
Unknown location (pc=0:{call_location}) Error message: Be aware of failure ahead... Unknown location (pc=0:{entry_point_location})
shouldn't it be here...?
Suggestion:
Error message: Be aware of failure ahead...
Error at pc=0:37:
Cairo traceback (most recent call last):
Unknown location (pc=0:{call_location})
Unknown location (pc=0:{entry_point_location})
8d5adef
to
998385b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 4 of 4 files at r4, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @TzahiTaub)
998385b
to
142721b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @TzahiTaub)
This change is