Adrian Reber 9d8b23d5dc 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>		2026-03-25 04:31:18 +01:00
..
riscv64-cross	ci: add workflow for riscv64	2025-03-21 12:40:31 -07:00
asan.sh	ci: stop testing ubuntu overlayfs	2023-10-22 13:29:25 -07:00
ci-after-success.sh	CI: rename 'travis' to 'ci'	2020-11-08 14:04:12 -08:00
docker-test.sh	ci: also exclude docker version 29	2025-12-14 17:28:58 +09:00
docker.env	ci: Re-enable zdtm/static/binfmt_misc	2026-02-17 17:07:29 +00:00
java-test.sh	ci: use package-manager dependency install scripts	2025-11-02 07:48:23 -08:00
loongarch64-qemu-test.sh	ci: use package-manager dependency install scripts	2025-11-02 07:48:23 -08:00
Makefile	ci: fix podman pids limit for thread-bomb test	2026-03-25 04:31:18 +01:00
podman-test.sh	ci/podman: show mounts	2024-09-11 16:02:11 -07:00
prepare-for-fedora-rawhide.sh	Use command -v instead of which	2025-11-05 15:41:34 -08:00
run-ci-tests.sh	ci: stabilize gcov-test coverage upload	2026-03-11 15:10:23 -07:00
vagrant.sh	Remove travis-ci leftovers	2025-11-02 07:48:23 -08:00