dilim/containerd
1
0
Fork 0
mirror of https://github.com/containerd/containerd.git synced 2026-08-09 01:21:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

ci: bound Go fuzzing by execution count

Browse Source 
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>
This commit is contained in:
Chris Henzie
2026-07-09 16:13:34 -07:00
parent 90eeccdecf
commit c1b9b78f47
1 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
script/go-test-fuzz.sh
View File

@@ -14,14 +14,16 @@
# See the License for the specific language governing permissions and
# limitations under the License.
# Running Go 1.18's fuzzing for 60 seconds each. While this would be too
# 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.
# 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
fuzztime=60s
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)
@@ -31,5 +33,5 @@ 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=$fuzztime
done
go test -fuzz=$fuzz_name ./$pkg_path -fuzztime=$fuzzlimit
done