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

Please add a description for fuzzer output columns #248

Open
fmstephe opened this issue May 23, 2019 · 3 comments
Open

Please add a description for fuzzer output columns #248

fmstephe opened this issue May 23, 2019 · 3 comments

Comments

@fmstephe
Copy link

There are two columns whose meaning are unclear to me.

Cover - this is not a percent value, so a description would help to interpret this.

Restarts - it’s unclear to me what causes the fuzzer to restart. There is an indication that you should aim to restart 1/1000 but it’s not clear how to influence this.

@josharian
Copy link
Collaborator

Yes, we should document these in the readme.

I actually think we shouldn’t display restarts at all, but instead monitor them and print a warning on stderr as needed; the warning could explain the problem more fully.

@dvyukov
Copy link
Owner

dvyukov commented May 24, 2019

I agree restarts is not very useful as is.
Cover percent is quite hard to do in a meaningful way. Ideally we need to understand what's potentially coverable and use it as max. But this is non-trivial to do. And it we do percent out of all linked in code, then the percent will be sadly small and won't be meangful anyway.

@fmstephe
Copy link
Author

For myself I would be happy with any reasonable, and rough, description of coverage. It doesn't need to be a percentage value. But since it isn't it would be nice to have an idea of what this ever increasing number actually is.

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

No branches or pull requests

3 participants