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
The last bug that remained in the EVM test suite highlights the importance of writing tests two ways: where the "base" (e.g. root of call frame tree) context is either
CONTRACT_CREATION
MESSAGE_CALL
Specifically the issue was when exploring the scenario/CALL_EOA_SUCCESS_WILL_REVERT where the caller was undergoing deployment and the deployment reverted. The issue was that when "undoing" the CALL at REVERT time we were using a more updated snapshot of the caller account, specifically one where the deployment had already been reverted. This clashed with account_consistency constraints.
The text was updated successfully, but these errors were encountered:
The last bug that remained in the EVM test suite highlights the importance of writing tests two ways: where the "base" (e.g. root of call frame tree) context is either
CONTRACT_CREATION
MESSAGE_CALL
Specifically the issue was when exploring the
scenario/CALL_EOA_SUCCESS_WILL_REVERT
where the caller was undergoing deployment and the deployment reverted. The issue was that when "undoing" the CALL at REVERT time we were using a more updated snapshot of the caller account, specifically one where the deployment had already been reverted. This clashed withaccount_consistency
constraints.The text was updated successfully, but these errors were encountered: