You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: