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.