Chris Henzie b452f28560 ci: bound Go fuzzing by execution count ...

Go can report context deadline exceeded when a duration-based fuzz limit
expires (https://go.dev/issue/75804).

Use a 50,000-execution limit based on the roughly 47,000 executions
FuzzImageStore completed in 30 seconds in CI. This keeps work stable
across runners and avoids the duration issue.

Assisted-by: Codex
(cherry picked from commit c1b9b78f47)
Signed-off-by: Chris Henzie <chrishenzie@gmail.com>

2026-07-13 14:33:13 -07:00

..

setup

Update go to 1.26.5/1.25.12

2026-07-07 16:57:36 -07:00

test

add use systemd cgroup e2e

2024-10-03 00:37:29 +08:00

vm

CI: migrate Vagrant to Lima

2026-07-10 04:38:48 +09:00

critest.sh

fix unbound SKIP_TEST variable error

2025-05-02 02:01:00 +00:00

go-test-fuzz.sh

ci: bound Go fuzzing by execution count

2026-07-13 14:33:13 -07:00

verify-go-modules.sh

fix verify-vendor if go.mod does not contain replace rules

2022-05-27 12:57:12 +02:00