From: Junio C Hamano <gitster@pobox.com>
To: Josh Steadmon <steadmon@google.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/2] Run limited fuzz tests in GitHub CI
Date: Fri, 19 Jan 2024 14:28:50 -0800 [thread overview]
Message-ID: <xmqqil3phs9p.fsf@gitster.g> (raw)
In-Reply-To: <cover.1705700054.git.steadmon@google.com> (Josh Steadmon's message of "Fri, 19 Jan 2024 13:38:11 -0800")
Josh Steadmon <steadmon@google.com> writes:
> Add a simple smoke test in CI to make sure that the fuzz tests can build
> and execute properly. While we already compile the fuzz-test objects in
> the default make target, we don't link the executables due to these
> requiring clang-specific support. However, this means that the fuzz
> tests have been vulnerable to unnoticed build breakages as the code that
> they link against has changed over time.
>
> Adding this CI test should make such build breakages more visible more
> quickly.
Nice.
> Josh Steadmon (2):
> fuzz: fix fuzz test build rules
> ci: build and run minimal fuzzers in GitHub CI
>
> .github/workflows/main.yml | 11 +++++++++++
> Makefile | 17 +++++++++++------
> ci/run-build-and-minimal-fuzzers.sh | 19 +++++++++++++++++++
> oss-fuzz/dummy-cmd-main.c | 14 ++++++++++++++
> 4 files changed, 55 insertions(+), 6 deletions(-)
> create mode 100755 ci/run-build-and-minimal-fuzzers.sh
> create mode 100644 oss-fuzz/dummy-cmd-main.c
>
>
> base-commit: 186b115d3062e6230ee296d1ddaa0c4b72a464b5
prev parent reply other threads:[~2024-01-19 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 21:38 [PATCH 0/2] Run limited fuzz tests in GitHub CI Josh Steadmon
2024-01-19 21:38 ` [PATCH 1/2] fuzz: fix fuzz test build rules Josh Steadmon
2024-01-19 22:46 ` Junio C Hamano
2024-03-04 18:57 ` Josh Steadmon
2024-01-19 21:38 ` [PATCH 2/2] ci: build and run minimal fuzzers in GitHub CI Josh Steadmon
2024-01-19 22:28 ` Junio C Hamano [this message]
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=xmqqil3phs9p.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=steadmon@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).