git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/2] fuzz: fix fuzz test build rules

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 19, 2024, 22:46 UTC
Message-ID
<xmqqcytxhrgs.fsf@gitster.g>
In-Reply-To
<9332e225e44b29be25d10229b05f0b9775b85568.1705700054.git.steadmon@google.com>
Josh Steadmon <steadmon@google.com> writes:
> @@ -762,7 +763,7 @@ fuzz-objs: $(FUZZ_OBJS)
>  # Always build fuzz objects even if not testing, to prevent bit-rot.
>  all:: $(FUZZ_OBJS)

So, this is what you referred to in your proposed log message. We do build objects to prevent bit-rot, but we do not link, so it is merely half a protection.

> ...
>  fuzz-all: $(FUZZ_PROGRAMS)

But there is this target. I wonder if it makes it even better to update the "always build fuzz objects" one? Given that some folks may not have the necessary clang toochain for linking, it may probably be a bit too much, perhaps?

It definitely is an improvement to build them in the CI environment, like you have in [2/2].

Thanks.  Will queue.
Previous: Josh SteadmonNext: Josh Steadmon
Message 3 of 6 in “Run limited fuzz tests in GitHub CI”
  1. 0/2 Run limited fuzz tests in GitHub CIJosh Steadmon, Jan 19, 2024
  2. 1/2 fuzz: fix fuzz test build rulesJosh Steadmon, Jan 19, 2024
  3. Junio C HamanoJan 19, 2024
  4. Josh SteadmonMar 4, 2024
  5. 2/2 ci: build and run minimal fuzzers in GitHub CIJosh Steadmon, Jan 19, 2024
  6. Junio C HamanoJan 19, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.