You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also a weird value is shown on the View page for L1->L2 transactions, with value: 79,598,458,911,708,134,998 (T)
How to reproduce:
To locally reproduce error, to try and debug, execute: forge test --match-contract ZkSyncAdapterTest --match-test test_receiveMessage -vvvv
on the code on this branch
This will execute a test that forks zksync-sepolia on the block of the failing transaction. This test calls the same method as the failing tx with the expected aliased caller. It checks that all the on chain configs are correct, previous to the call, and checks that all the expected events and state changes happen after the call (It uses the deployed addresses, without using mocks).
The problem is that the test execution on the fork works as it should, while the execution on the testnet chain doesn't.
This was done using the dev branch of foundry-zksync
The text was updated successfully, but these errors were encountered:
Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.0.2 (1f3160e 2024-05-30T00:22:09.630097000Z)
What command(s) is the bug in?
No response
Operating System
macOS (Apple Silicon)
Describe the bug
Problem:
Trouble debugging why a bridging transaction fails on zksync-sepolia side.
Also a weird value is shown on the View page for L1->L2 transactions, with value: 79,598,458,911,708,134,998 (T)
How to reproduce:
To locally reproduce error, to try and debug, execute:
forge test --match-contract ZkSyncAdapterTest --match-test test_receiveMessage -vvvv
on the code on this branch
This will execute a test that forks zksync-sepolia on the block of the failing transaction. This test calls the same method as the failing tx with the expected aliased caller. It checks that all the on chain configs are correct, previous to the call, and checks that all the expected events and state changes happen after the call (It uses the deployed addresses, without using mocks).
The problem is that the test execution on the fork works as it should, while the execution on the testnet chain doesn't.
This was done using the dev branch of foundry-zksync
The text was updated successfully, but these errors were encountered: