ci: fix podman pids limit for thread-bomb test

The --pids-limit=0 value does not disable the pids limit in
current podman versions. The podman documentation specifies
that -1 means unlimited. With --pids-limit=0, the thread-bomb
test fails on the second run (after restore) because each of
the 1024 threads tries to create a new thread, exceeding the
container's pids limit and causing pthread_create() to return
EAGAIN.

Change --pids-limit=0 to --pids-limit=-1 to properly disable
the pids cgroup limit.

Assisted-by: Claude:claude-opus-4-6
Signed-off-by: Adrian Reber <areber@redhat.com>
This commit is contained in:
Adrian Reber 2026-03-16 16:12:37 +00:00 committed by Radostin Stoyanov
parent 4bcf08ce7f
commit 9d8b23d5dc

View file

@ -41,7 +41,7 @@ endif
ifeq ($(CONTAINER_RUNTIME),podman)
# Podman limits the number of processes in a container using cgroups.
# Disable it as it breaks the thread-bomb test
CONTAINER_OPTS += --pids-limit=0
CONTAINER_OPTS += --pids-limit=-1
endif
export ZDTM_OPTS