opencontainers / opencontainers/runc
flaky test: TestProcessEmptyCaps
Open
Nobody has claimed this yet.
area/ci
- Dominant language
- Go
- Stars
- 13.5k
- Forks
- 2.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 30
Description
I've started seeing this error in CI more often recently (in GHA CI runs). I suspect there's a race with the kernel creating the cgroup dentries. Maybe we should have some retry code? Idk.
=== RUN TestProcessEmptyCaps
time="2023-12-07T04:19:25Z" level=warning msg="unable to get oom kill count" error="openat2 /sys/fs/cgroup/memory/test/integration/memory.oom_control: no such file or directory"
exec_test.go:299: unexpected error: unable to start container process: unable to apply cgroup configuration: openat2 /sys/fs/cgroup/cpuset/test/integration/cpuset.mems: no such file or directory
--- FAIL: TestProcessEmptyCaps (0.13s)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with TestProcessEmptyCaps and the failure reported at exec_test.go:299 in GHA CI. Investigate the missing cgroup dentries and determine whether the failure is a race; done means the test no longer flakes in the affected CI runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100