From: Darren Kenny <darren.kenny@oracle.com>
To: Alexander Bulekov <alxndr@bu.edu>, qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
qemu-trivial@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Alexander Bulekov" <alxndr@bu.edu>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH] gitlab-ci.yml: Only run one test-case per fuzzer
Date: Fri, 02 Oct 2020 16:22:42 +0100 [thread overview]
Message-ID: <m27ds87iv1.fsf@oracle.com> (raw)
In-Reply-To: <20201002143524.56930-1-alxndr@bu.edu>
On Friday, 2020-10-02 at 10:35:24 -04, Alexander Bulekov wrote:
> With 1000 runs, there is a non-negligible chance that the fuzzer can
> trigger a crash. With this CI job, we care about catching build/runtime
> issues in the core fuzzing code. Actual device fuzzing takes place on
> oss-fuzz. For these purposes, only running one input should be
> sufficient.
>
> Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
> Suggested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Darren Kenny <darren.kenny@oracle.com>
> ---
> .gitlab-ci.yml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index a51c89554f..075c15d45c 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -303,7 +303,7 @@ build-oss-fuzz:
> | grep -v slirp); do
> grep "LLVMFuzzerTestOneInput" ${fuzzer} > /dev/null 2>&1 || continue ;
> echo Testing ${fuzzer} ... ;
> - "${fuzzer}" -runs=1000 -seed=1 || exit 1 ;
> + "${fuzzer}" -runs=1 -seed=1 || exit 1 ;
> done
> # Unrelated to fuzzer: run some tests with -fsanitize=address
> - cd build-oss-fuzz && make check-qtest-i386 check-unit
> --
> 2.28.0
WARNING: multiple messages have this Message-ID (diff)
From: Darren Kenny <darren.kenny@oracle.com>
To: Alexander Bulekov <alxndr@bu.edu>, qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
qemu-trivial@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Alexander Bulekov" <alxndr@bu.edu>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH] gitlab-ci.yml: Only run one test-case per fuzzer
Date: Fri, 02 Oct 2020 16:22:42 +0100 [thread overview]
Message-ID: <m27ds87iv1.fsf@oracle.com> (raw)
In-Reply-To: <20201002143524.56930-1-alxndr@bu.edu>
On Friday, 2020-10-02 at 10:35:24 -04, Alexander Bulekov wrote:
> With 1000 runs, there is a non-negligible chance that the fuzzer can
> trigger a crash. With this CI job, we care about catching build/runtime
> issues in the core fuzzing code. Actual device fuzzing takes place on
> oss-fuzz. For these purposes, only running one input should be
> sufficient.
>
> Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
> Suggested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Darren Kenny <darren.kenny@oracle.com>
> ---
> .gitlab-ci.yml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index a51c89554f..075c15d45c 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -303,7 +303,7 @@ build-oss-fuzz:
> | grep -v slirp); do
> grep "LLVMFuzzerTestOneInput" ${fuzzer} > /dev/null 2>&1 || continue ;
> echo Testing ${fuzzer} ... ;
> - "${fuzzer}" -runs=1000 -seed=1 || exit 1 ;
> + "${fuzzer}" -runs=1 -seed=1 || exit 1 ;
> done
> # Unrelated to fuzzer: run some tests with -fsanitize=address
> - cd build-oss-fuzz && make check-qtest-i386 check-unit
> --
> 2.28.0
next prev parent reply other threads:[~2020-10-02 15:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 14:35 [PATCH] gitlab-ci.yml: Only run one test-case per fuzzer Alexander Bulekov
2020-10-02 14:35 ` Alexander Bulekov
2020-10-02 14:43 ` Philippe Mathieu-Daudé
2020-10-02 15:15 ` Thomas Huth
2020-10-02 15:15 ` Thomas Huth
2020-10-02 15:53 ` Philippe Mathieu-Daudé
2020-10-02 15:56 ` Thomas Huth
2020-10-02 18:47 ` Alexander Bulekov
2020-10-02 18:47 ` Alexander Bulekov
2020-10-02 15:22 ` Darren Kenny [this message]
2020-10-02 15:22 ` Darren Kenny
2020-10-12 10:00 ` Thomas Huth
2020-10-12 10:00 ` Thomas Huth
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=m27ds87iv1.fsf@oracle.com \
--to=darren.kenny@oracle.com \
--cc=alex.bennee@linaro.org \
--cc=alxndr@bu.edu \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.