Skip to content

fix: remove --pids-limit=0 to fix pjdfstest truncate failures#225

Closed
claude-claude[bot] wants to merge 1 commit intohttp-proxyfrom
claude/fix-21682793781
Closed

fix: remove --pids-limit=0 to fix pjdfstest truncate failures#225
claude-claude[bot] wants to merge 1 commit intohttp-proxyfrom
claude/fix-21682793781

Conversation

@claude-claude
Copy link
Copy Markdown
Contributor

@claude-claude claude-claude bot commented Feb 4, 2026

CI Fix

Fixes CI #21682225880

Problem

The test test_pjdfstest_vm_truncate was failing consistently (all 3 retry attempts) with test #15 in truncate/00.t failing. This was caused by the --pids-limit=0 flag added in commit ff84469.

While --pids-limit=0 was intended to avoid cgroup pids controller errors by disabling pids limits entirely, it caused unexpected behavior in POSIX compliance tests that may rely on proper process constraints and resource limits.

Solution

Removed the --pids-limit=0 flag from podman arguments in fc-agent. The existing wait_for_cgroup_controllers() function should be sufficient to ensure the pids controller is available in the root cgroup's subtree_control before starting containers.

This allows containers to use proper process limits while still handling the cgroup initialization race condition through the wait mechanism.

Testing

  • Failing test: test_pjdfstest_vm_truncate (test Rust packaging for cargo install #15 in truncate/00.t)
  • Failed in: Host-Root-arm64-SnapshotDisabled and Host-Root-x64-SnapshotDisabled jobs
  • Should now pass with proper pids limit behavior restored

Generated by Claude | Fix Run

The --pids-limit=0 flag was causing test_pjdfstest_vm_truncate to fail
consistently (test #15 in truncate/00.t). While it was added to avoid
cgroup pids controller errors, disabling pids limits entirely can cause
unexpected behavior in tests that rely on proper process constraints.

The wait_for_cgroup_controllers() function should be sufficient to ensure
pids controller is available before starting containers, making the
--pids-limit=0 workaround unnecessary.

Fixes test failure in CI run #21682225880
@ejc3
Copy link
Copy Markdown
Owner

ejc3 commented Feb 4, 2026

Fix cherry-picked into http-proxy branch

@ejc3 ejc3 closed this Feb 4, 2026
@ejc3 ejc3 deleted the claude/fix-21682793781 branch February 8, 2026 18:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant