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
It is possible for echidna reproducers or corpus entries to have transactions that revert. When those transactions are converted to a foundry test, the whole test fails.
Code example to reproduce the issue:
It requires quite a bit of "luck" to generate one of those call sequences, as they are usually optimized during shrinking. But using a low value for the shrinking runs can help finding one, I guess.
Good point, although I'm unsure how to resolve this since Echidna/Medusa sequences don't contain any info on if the call reverted or not. We could ignore reverts by wrapping the call in a try/catch, albeit that would inflate the LOC a bit
Describe the issue:
It is possible for echidna reproducers or corpus entries to have transactions that revert. When those transactions are converted to a foundry test, the whole test fails.
Code example to reproduce the issue:
It requires quite a bit of "luck" to generate one of those call sequences, as they are usually optimized during shrinking. But using a low value for the shrinking runs can help finding one, I guess.
Version:
commit 4db6306 + PR #32
Relevant log output:
No response
The text was updated successfully, but these errors were encountered: