From 750a04b613d7d8e7de9ab18863ad2a27055b58a2 Mon Sep 17 00:00:00 2001 From: EuAndreh Date: Fri, 12 Jun 2026 23:35:12 -0300 Subject: tests: fuzz a fixed count (1000x), not a 1s wall-clock budget -fuzztime=1s is a wall-clock deadline; under parallel-build load the fuzzer's setup (worker spawn + baseline coverage) can overrun it and the run fails with "context deadline exceeded" --- a flake unrelated to the code. A count budget (1000x) has no wall-clock deadline: it always runs the seeds + 1000 iterations regardless of load, just slower when busy. Renamed FUZZSEC -> FUZZTIME since it is no longer seconds. Co-Authored-By: Claude Fable 5 --- Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index 65b1bb2..d32b5df 100644 --- a/Makefile +++ b/Makefile @@ -127,10 +127,10 @@ check: check-unit check-integration -FUZZSEC=1 +FUZZTIME=1000x fuzz/main.bin-check = $(fuzz/main.go:.go=.bin-check) $(fuzz/main.bin-check): - $(EXEC)$*.bin --test.fuzztime=$(FUZZSEC)s --test.parallel=$N \ + $(EXEC)$*.bin --test.fuzztime=$(FUZZTIME) --test.parallel=$N \ --test.fuzz='.*' --test.fuzzcachedir=tests/fuzz/corpus fuzz: $(fuzz/main.bin-check) -- cgit v1.3