Introduce fuzz tests for wrap_optimal_fit and wrap_first_fit #256
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These fuzz tests immediately found the problem reported in #247 and gave a short way of reproducing it:
will currently panic due to an overflow error. This is because the gap after
"x"
is enourmous, large enough to makecost += gap * gap
overflow thei32
type currently used for the cost computations.The
wrap_first_fit
function seems to not crash.Run the fuzz tests with:
You’ll need to
cargo install cargo-fuzz
first.