From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtpng2.m.smailru.net (smtpng2.m.smailru.net [94.100.179.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 5129245C305 for ; Mon, 7 Dec 2020 20:42:59 +0300 (MSK) Date: Mon, 7 Dec 2020 20:42:55 +0300 From: Igor Munkin Message-ID: <20201207174255.GH5396@tarantool.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Subject: Re: [Tarantool-patches] [PATCH 4/4] test: integrate with OSS Fuzz List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: sergeyb@tarantool.org Cc: tarantool-patches@dev.tarantool.org Sergey, Thanks for the patch! Please consider the singe nit below. On 30.11.20, sergeyb@tarantool.org wrote: > From: Sergey Bronnikov > > To run Tarantool fuzzers on OSS Fuzz infrastructure it is needed to pass > library $LIB_FUZZING_ENGINE to linker and use external CFLAGS and CXXFLAGS. > Full description how to integrate with OSS Fuzz is in [1] and [2]. Minor: The body of the commit message should be wrapped up to 72 characters (except the links I believe) according to our guidelines[1]. > > Patch to OSS Fuzz repository [2] is ready to merge. > > 1. https://google.github.io/oss-fuzz/getting-started/new-project-guide/ > 2. https://google.github.io/oss-fuzz/advanced-topics/ideal-integration/ > 3. https://github.com/google/oss-fuzz/pull/4723 > > Closes #1809 > --- > test/fuzz/CMakeLists.txt | 13 +++++++++++++ > 1 file changed, 13 insertions(+) > > -- > 2.25.1 -- Best regards, IM