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

[C++][CI] Enable continuous fuzzing #16753

Closed
asfimport opened this issue Jun 7, 2019 · 7 comments
Closed

[C++][CI] Enable continuous fuzzing #16753

asfimport opened this issue Jun 7, 2019 · 7 comments

Comments

@asfimport
Copy link

asfimport commented Jun 7, 2019

Since fuzzing kinda only works if done as a continuous background job, we should find a way of doing so. This likely requires another service than Travis. Basic requirements are:

  • master builds should be submitted for fuzzing
  • project members should be informed about new crashes (ideally not via public issue due to potential security impact)

Reporter: Marco Neumann / @crepererum
Assignee: Yevgeny Pats / @yevgenypats

Related issues:

PRs and other links:

Note: This issue was originally created as ARROW-5525. Please see the migration documentation for further details.

@asfimport
Copy link
Author

Wes McKinney / @wesm:
Issue resolved by pull request 4504
#4504

@asfimport
Copy link
Author

Antoine Pitrou / @pitrou:
@yevgenypats Can you explain how one can view the fuzzing jobs? I submitted a build from my local machine but don't know where to view it (I'm using the hardcoded API key):

2019/09/17 14:20:01 Creating job...
2019/09/17 14:20:02 Uploading fuzzer...
2019/09/17 14:20:39 Starting job
2019/09/17 14:20:39 Job aQbIQe0y2n4LX0iKYjnd started succesfully
2019/09/17 14:20:39 Job created successfully

@asfimport
Copy link
Author

Marco Neumann / @crepererum:
There's https://fuzzit.dev/ where you can login via GitHub, but I think your account must be linked to the apache/arrow organization (on Fuzzit, not on GitHub). That (to my understanding) must be done by the Fuzzit support team ( @yevgenypats ?).

@asfimport
Copy link
Author

Yevgeny Pats / @yevgenypats:
@pitrou  I've added you as admin to apache arrow organisation https://app.fuzzit.dev/orgs/yMxZh42xl9qy6bvg3EiJ/dashboard.

[~marco.neumann.by] you are admin in the organisation.

 

As far as I remember the fuzzing was a bit stalled as the arrow-ipc-fuzzing target was crashing constantly and it wasn't fix so it doesn't really accumulate any interesting corpus.

Also a lot was changed since we first integrated apache-arrow so if fuzzing is a again a priority I would love to help - transfer apache/arrow to new organisation (the old one was deprecated.) and update the Fuzzit CLI to latest version.

 

Also @pitrou  you can join our slack at https://slack.fuzzit.dev and DM so I can help you set it up.

@asfimport
Copy link
Author

Marco Neumann / @crepererum:

[~marco.neumann.by] you are admin in the organisation.
Didn't know that. @pitrou which mail address do you use for GitHub so I can add you to the Org?

 

As far as I remember the fuzzing was a bit stalled as the arrow-ipc-fuzzing target was crashing constantly and it wasn't fix so it doesn't really accumulate any interesting corpus.
I have tried to fix all known bugs and fixed the CI, so since some weeks it runs more or less smoothly again. One thing that we might change is to add some known arrow files to the seed corpus so we don't solely rely on the fuzzer to find valid files during the exploration.
Also a lot was changed since we first integrated apache-arrow so if fuzzing is a again a priority I would love to help - transfer apache/arrow to new organisation (the old one was deprecated.) and update the Fuzzit CLI to latest version.
That would help a lot I think.

@asfimport
Copy link
Author

Antoine Pitrou / @pitrou:
[~marco.neumann.by] I think it's pitrou@free.fr

@asfimport
Copy link
Author

Yevgeny Pats / @yevgenypats:
[~marco.neumann.by] ok, cool. I'll open a PR with an update. and I'll transfer you organisation to a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant