Skip to content
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 reverting LOGs and the impact on the MMU module and its STAMP #671

Open
4 tasks
letypequividelespoubelles opened this issue Apr 9, 2024 · 1 comment
Open
4 tasks
Labels

Comments

@letypequividelespoubelles
Copy link
Collaborator

We must ensure that the MMU_STAMP from the HUB and the MMU module are in sync, see #397. We should thus have tests with

  • reverted internal transactions that produce (reverted) LOG's
    • with reverts caused by the current context (CONTEXT_SELF_REVERT = 1)
    • and with reverts caused by some parent context reverting (CONTEXT_GETS_REVERTED = 1)
  • both reverted and unreverted LOG's
@letypequividelespoubelles
Copy link
Collaborator Author

linked with #670

@lorenzogentile404 lorenzogentile404 changed the title MMU_STAMP coherence tests Test reverting LOGs and the impact on the MMU module and its STAMP Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant