[
https://issues.apache.org/jira/browse/ARROW-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16931563#comment-16931563
]
Yevgeny Pats commented on ARROW-5525:
-------------------------------------
[~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|https://slack.fuzzit.dev/] and DM so I can help you
set it up.
> [C++][CI] Enable continuous fuzzing
> -----------------------------------
>
> Key: ARROW-5525
> URL: https://issues.apache.org/jira/browse/ARROW-5525
> Project: Apache Arrow
> Issue Type: Test
> Components: C++
> Reporter: Marco Neumann
> Assignee: Yevgeny Pats
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.15.0
>
> Time Spent: 6.5h
> Remaining Estimate: 0h
>
> 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)
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
