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

Consider displaying assertion failure immediately once falsified in text mode #1205

Closed
0xicingdeath opened this issue Mar 12, 2024 · 1 comment · Fixed by #1271
Closed

Consider displaying assertion failure immediately once falsified in text mode #1205

0xicingdeath opened this issue Mar 12, 2024 · 1 comment · Fixed by #1271

Comments

@0xicingdeath
Copy link

Describe the desired feature

In the UI mode, the interface will show you that there is a failed assertion, and its attempt to shrink the call sequence into something shorter.

In text mode, when a property is falsified, it only tells you that the property has been falsified, and requires you to wait until Echidna finishes execution in order to tell you what exactly failed. For projects with large corpuses (replays taking up 3-5 minutes, depending on machine), this becomes a very time-intensive process.

Instead, it would be great if the logs in text mode contained the assertion failure or call sequence that resulted in the failure, as well as the assertion failure in question, while executing – this would allow us to start debugging, while letting Echidna continue to run through its execution.

@ggrieco-tob
Copy link
Member

This will be really helpful and should not be too hard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants