[
https://issues.apache.org/jira/browse/ARROW-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16931568#comment-16931568
]
Marco Neumann commented on ARROW-5525:
--------------------------------------
{quote}[~marco.neumann.by] you are admin in the organisation.
{quote}
Didn't know that. [~pitrou] which mail address do you use for GitHub so I can
add you to the Org?
{quote}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.
{quote}
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.
{quote}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.
{quote}
That would help a lot I think.
> [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)
