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.

Sign up for GitHub

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

Jump to bottom

Awww it's so fuzzy! #49

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Awww it's so fuzzy! #49

wants to merge 4 commits into from

Commits on Dec 8, 2017

  1. Make fuzzer use debug assertions

    @killercup
    killercup committed Dec 8, 2017
    Configuration menu
    Copy the full SHA
    021fbd4 View commit details
    Browse the repository at this point in the history

  2. Add a Readme to fuzzer directory

    @killercup
    killercup committed Dec 8, 2017
    Configuration menu
    Copy the full SHA
    2a93c76 View commit details
    Browse the repository at this point in the history

  3. Run fuzzer for 20 seconds on travis 

    I think it's fine to run this *and fail CI on it* because in my
experience nobody will notice that it's broken otherwise. Additionally,
the fuzzer here seems pretty stable. And if it actually found a panic,
you should know about it.
    @killercup
    killercup committed Dec 8, 2017
    Configuration menu
    Copy the full SHA
    dc092c7 View commit details
    Browse the repository at this point in the history

  4. Pascal vs. Travis 

    (will amend and force-push this commit until it's green)
    @killercup
    killercup committed Dec 8, 2017
    Configuration menu
    Copy the full SHA
    419489e View commit details
    Browse the repository at this point in the history