Chris Henzie 71e00ba9c1 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:58:22 -07:00

test

*: add DrainExecSyncIOTimeout config and disable as by default

2023-03-03 00:21:55 +08:00

critest.sh

fix unbound SKIP_TEST variable error

2025-05-06 03:32:33 +00:00

go-test-fuzz.sh

ci: bound Go fuzzing by execution count

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

resize-vagrant-root.sh

Ignore NOCHANGE error

2026-03-19 14:28:35 +00:00

verify-go-modules.sh

Add api go submodule

2024-06-13 06:22:21 -07:00