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

Mutant failures caused by timeouts need to be more prominent #1251

Open
dkubb opened this issue Aug 27, 2021 · 0 comments
Open

Mutant failures caused by timeouts need to be more prominent #1251

dkubb opened this issue Aug 27, 2021 · 0 comments

Comments

@dkubb
Copy link
Collaborator

dkubb commented Aug 27, 2021

When mutant fails because of a timeout violation it would be nice to have it more prominent. Especially when that failure results in a noop. I had some failures that seemed intermittent but it wasn't until @mbj pointed out the error logs that I could see there was a timeout error responsible for the noop.

My high level suggestion would be that there should be a summary of the failure as the very last thing printed to the screen before exiting. Then if I want more detail I can scroll up and dig in, but the summary would've been helpful in identifying the cause more early.

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

No branches or pull requests

1 participant