Skip to content

Move libfuzzer to a separate package #5247

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

Closed
brson opened this issue Mar 6, 2013 · 8 comments
Closed

Move libfuzzer to a separate package #5247

brson opened this issue Mar 6, 2013 · 8 comments
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@brson
Copy link
Contributor

brson commented Mar 6, 2013

(Original title: "Remove the fuzzer")

This code is very bitrotted.

@brson
Copy link
Contributor Author

brson commented Mar 6, 2013

@jruderman opinions?

@erickt
Copy link
Contributor

erickt commented Mar 7, 2013

We should factor this out into a cargo (or whatever we're calling the third party packages nowadays). It's a shame it didn't really get used, but it could be really useful if modernized.

@graydon
Copy link
Contributor

graydon commented Mar 7, 2013

I'd like to do quite a lot of work on quickcheck-like and random testing; just keep deferring due to more pressing stuff

@graydon
Copy link
Contributor

graydon commented Jun 6, 2013

Still undecided as of 2013-06-05. I support moving it to a separate package at this point (or as soon as rustpkg is sufficiently mature to handle that). In general I want to make a package that deals with formal grammars (BNF) and can both parse/print them and do combinatorial random generation on them.

@pcwalton
Copy link
Contributor

I don't think this is backwards incompatible.

@brson
Copy link
Contributor Author

brson commented Jun 15, 2013

This code is seriously bitrotted. It has not been used in years - much of it isn't even included in the build. Not suggesting we shouldn't do fuzzing, nor that it isn't appropriate to live in-tree, but this code is never going to be used again.

@graydon
Copy link
Contributor

graydon commented Jun 15, 2013

Agreed

bors added a commit that referenced this issue Jun 16, 2013
It is suffering from a bad case of megabitrot. #5247
@z0w0
Copy link
Contributor

z0w0 commented Aug 7, 2013

Closing, fuzzer was removed in #7166.

@z0w0 z0w0 closed this as completed Aug 7, 2013
bors added a commit to rust-lang-ci/rust that referenced this issue May 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Development

No branches or pull requests

5 participants