Files
containerd/script/go-test-fuzz.sh
Chris Henzie c1b9b78f47 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
Signed-off-by: Chris Henzie <chrishenzie@gmail.com>
2026-07-09 16:45:11 -07:00

38 lines
1.4 KiB
Bash
Executable File

#!/usr/bin/env bash
# Copyright The containerd Authors.
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
# http://www.apache.org/licenses/LICENSE-2.0
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# Running Go's fuzzing for 50,000 executions. While this would be too
# short to actually find issues, we want to make sure that these fuzzing
# tests are not fundamentally broken. Using an execution limit rather than a
# duration also avoids spurious failures when a duration expires
# (https://go.dev/issue/75804).
set -euo pipefail
set -x
fuzzlimit=50000x
# keep the filename and Fuzz function name so we can run every fuzz test
# in a package separately (`go test -fuzz` only supports single fuzz function)
pkgs=$(git grep 'func Fuzz.*testing\.F' | grep -o '.*testing\.F)' | grep -v -E "vendor" | sort | uniq)
IFS=$'\n'
for pkg in $pkgs
do
pkg_path=$(echo $pkg | grep -o '.*/')
fuzz_name=$(echo $pkg | grep -o 'Fuzz[^(]*')
go test -fuzz=$fuzz_name ./$pkg_path -fuzztime=$fuzzlimit
done