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

cmd/go: change meaning of "total" in output while fuzzing #51023

Closed
katiehockman opened this issue Feb 4, 2022 · 1 comment
Closed

cmd/go: change meaning of "total" in output while fuzzing #51023

katiehockman opened this issue Feb 4, 2022 · 1 comment
Labels
FrozenDueToAge fuzz Issues related to native fuzzing support NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@katiehockman
Copy link
Contributor

The current log message during fuzzing looks like the following:

fuzz: elapsed: 0s, gathering baseline coverage: 0/23 completed
fuzz: elapsed: 0s, gathering baseline coverage: 23/23 completed, now fuzzing with 6 workers
fuzz: elapsed: 3s, execs: 5420 (1806/sec), new interesting: 2 (total: 21)

What the "total" refers to is a bit confusing, and the output above looks like a bug when it isn't. It currently means the total size of the generated corpus, but it would be clearer if it was the entire corpus size.

This should not require a freeze exception because it is fixing an issue with the log output (not changing any functionality) of a new feature introduced in this release.

See #50913 (comment)

/cc @AlekSi @golang/fuzzing

@katiehockman katiehockman added NeedsFix The path to resolution is known, but the work has not been done. fuzz Issues related to native fuzzing support labels Feb 4, 2022
@katiehockman katiehockman added this to the Go1.18 milestone Feb 4, 2022
@katiehockman katiehockman changed the title cmd/go: update log message while fuzzing cmd/go: change meaning of "total" in output while fuzzing Feb 4, 2022
@katiehockman katiehockman self-assigned this Feb 4, 2022
@gopherbot
Copy link

Change https://golang.org/cl/383414 mentions this issue: internal/fuzz: change meaning of "total" in output

@golang golang locked and limited conversation to collaborators Jun 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge fuzz Issues related to native fuzzing support NeedsFix The path to resolution is known, but the work has not been done.
Projects
Status: No status
Development

No branches or pull requests

2 participants