From: Serge Petrenko <sergepetrenko@tarantool.org> To: sergeyb@tarantool.org, tarantool-patches@dev.tarantool.org, imun@tarantool.org Subject: Re: [Tarantool-patches] [PATCH 0/4] Add fuzzing testing Date: Tue, 1 Dec 2020 13:54:14 +0300 [thread overview] Message-ID: <078cfd39-f07c-3f7c-8023-9b8b584d7d71@tarantool.org> (raw) In-Reply-To: <cover.1606766417.git.sergeyb@tarantool.org> 30.11.2020 23:24, sergeyb@tarantool.org пишет: > From: Sergey Bronnikov <sergeyb@tarantool.org> > > Patch series adds required support in project infrastructure for fuzzing tests, > add tests for uri, csv and http_parser modules, adds integration with OSS Fuzz > (infrastructure for continuous running fuzzing tests). > > NOTE: v2 version had LGTM from Sergey Petrenko, see [1] > > Changelog: > > v2: > - introduce CMake flag to enable building fuzzers > - add fuzzers based on LibFuzzer to csv, http_parser and uri modules > > v3: > - report error on an attempt to set ENABLE_FUZZER=ON with GCC compiler > - fixed return code in tests > - place tests to a common dir test/fuzz/ like we did with unit tests > - enable building fuzzers in Tarantool CI job > - add target to build all availabe fuzzers > - add integration with OSS Fuzz [2] > - add corpus for uri, csv and http_parser tests > > 1. https://lists.tarantool.org/pipermail/tarantool-patches/2020-April/016471.html > 2. https://github.com/google/oss-fuzz/pull/4723 > > CI: https://gitlab.com/tarantool/tarantool/-/pipelines/223112908 > Issue: https://github.com/tarantool/tarantool/issues/1809 Hi! Thanks for the patchset! Generally LGTM with one question. > > Sergey Bronnikov (4): > test: add infrastructure for fuzzing testing and fuzzers > test: add corpus to be used with fuzzers > travis: build tarantool with ENABLE_FUZZER Why travis? Don't we use gitlab for all the QA jobs? Is travis.mk shared between gitlab and travis? > test: integrate with OSS Fuzz > -- Serge Petrenko
next prev parent reply other threads:[~2020-12-01 10:54 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-30 20:24 sergeyb 2020-11-30 20:24 ` [Tarantool-patches] [PATCH 1/4] test: add infrastructure for fuzzing testing and fuzzers sergeyb 2020-12-07 17:24 ` Igor Munkin 2020-12-07 19:54 ` Igor Munkin 2020-12-13 18:56 ` Sergey Bronnikov 2020-12-20 13:31 ` Igor Munkin 2020-12-24 10:18 ` Sergey Bronnikov 2020-12-24 13:22 ` Igor Munkin 2020-12-24 17:25 ` Sergey Bronnikov 2020-12-24 17:50 ` Igor Munkin 2020-12-25 7:07 ` Sergey Bronnikov 2020-12-25 9:02 ` Igor Munkin 2020-12-25 10:33 ` Sergey Bronnikov 2020-11-30 20:24 ` [Tarantool-patches] [PATCH 2/4] test: add corpus to be used with fuzzers sergeyb 2020-12-07 17:34 ` Igor Munkin 2020-12-13 18:56 ` Sergey Bronnikov 2020-11-30 20:24 ` [Tarantool-patches] [PATCH 3/4] travis: build tarantool with ENABLE_FUZZER sergeyb 2020-12-07 17:38 ` Igor Munkin 2020-11-30 20:24 ` [Tarantool-patches] [PATCH 4/4] test: integrate with OSS Fuzz sergeyb 2020-12-07 17:42 ` Igor Munkin 2020-12-01 10:54 ` Serge Petrenko [this message] 2020-12-01 14:41 ` [Tarantool-patches] [PATCH 0/4] Add fuzzing testing Sergey Bronnikov 2020-12-01 14:45 ` Serge Petrenko 2020-12-07 17:49 ` Igor Munkin 2020-12-25 13:08 ` Igor Munkin 2020-12-25 14:52 ` Kirill Yukhin
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=078cfd39-f07c-3f7c-8023-9b8b584d7d71@tarantool.org \ --to=sergepetrenko@tarantool.org \ --cc=imun@tarantool.org \ --cc=sergeyb@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 0/4] Add fuzzing testing' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox