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

use the correct return values in Fuzz() functions #2705

Merged
merged 1 commit into from
Aug 17, 2020

Conversation

marten-seemann
Copy link
Member

The docs say:

Data is a random input generated by go-fuzz, note that in most cases it is invalid. The function must return 1 if the fuzzer should increase priority of the given input during subsequent fuzzing (for example, the input is lexically correct and was parsed successfully); -1 if the input must not be added to corpus even if gives new coverage; and 0 otherwise; other values are reserved for future use.

@codecov
Copy link

codecov bot commented Aug 8, 2020

Codecov Report

Merging #2705 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2705   +/-   ##
=======================================
  Coverage   86.77%   86.77%           
=======================================
  Files         124      124           
  Lines        9893     9893           
=======================================
  Hits         8584     8584           
  Misses        979      979           
  Partials      330      330           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d7c2169...720f81c. Read the comment docs.

@marten-seemann marten-seemann merged commit 2748efb into master Aug 17, 2020
@marten-seemann marten-seemann deleted the improve-fuzz-return-values branch August 17, 2020 23:54
@aschmahmann aschmahmann mentioned this pull request Sep 22, 2020
72 tasks
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

Successfully merging this pull request may close these issues.

2 participants