gas data tests across execution entry points#26179
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
36044db to
e8f18cb
Compare
tzakian
left a comment
There was a problem hiding this comment.
One question on a test but otherwise LGTM
| } | ||
| _ => unreachable!(), | ||
| }; | ||
| println!("{entry_point}: {result:?}"); |
There was a problem hiding this comment.
Should there be an assertion on the result here?
There was a problem hiding this comment.
well definitely there should NOT be a println
alex-mysten
left a comment
There was a problem hiding this comment.
This looks good to me - one comment - happy to add the address balance / gasless variants once merged
| // ============================================================================= | ||
|
|
||
| #[tokio::test] | ||
| async fn test_simple_transfer_gas_all_paths() { |
There was a problem hiding this comment.
what about a valid gas coin with insufficient balance for gas_budget? thinking about how that would translate to address balances too
There was a problem hiding this comment.
we should have those tests elsewhere, this was mostly to track bad gas data and transaction data related to gas.
To be honest I would like to review all gas tests because we had few issues and I believe we can organize them better
e8f18cb to
3a8e587
Compare
|
addressed feedback |
3a8e587 to
8aad53b
Compare
## Description We check that bad gas data produces expected and consistent results across entry point. Bogus data for address balance and free transaction is not really exercised yet and should come with a later PR (@mystenmark @alex-mysten @aschran if you have suggestions) Co-Authored-By: My Dog (1M bones) <noreply@my_dog.com> and Claude Opus 4.6 (1M context) <noreply@anthropic.com> ## Test plan This is it --- ## Release notes Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required. For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates. - [ ] Protocol: - [ ] Nodes (Validators and Full nodes): - [ ] gRPC: - [ ] JSON-RPC: - [ ] GraphQL: - [ ] CLI: - [ ] Rust SDK: - [ ] Indexing Framework:
Description
We check that bad gas data produces expected and consistent results across entry point.
Bogus data for address balance and free transaction is not really exercised yet and should come with a later PR (@mystenmark @alex-mysten @aschran if you have suggestions)
Co-Authored-By: My Dog (1M bones) <noreply@my_dog.com> and Claude Opus 4.6 (1M context) noreply@anthropic.com
Test plan
This is it
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.