-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(regression in master) not ok 117 update devices [minimal transition rules] #3014
Comments
Got it again on the same PR, the only difference is go version (1.15 this time). Hmm, maybe it is related to the changes I made in #3011. From https://github.com/opencontainers/runc/runs/2787301089?check_suite_focus=true:
|
Created #3015 to investigate |
Bad news -- I was able to reproduce this on master branch (see PR #3015), CI job https://github.com/opencontainers/runc/pull/3015/checks?check_run_id=2787947078. Either we broke something recently, or it was always like that, I dunno. |
Adding 1.0.0 milestone just in case we did broke something recently (it's not yet clear). |
A few more failures recently with the same issue
The last one is the oldest, it failed 3 days ago. |
Shit, I think I did a very bad thing. We need to revert #2994. |
Got an error from CI for PR #3011, during test (1.16.x) integration test with systemd. Also reproducible on master and other recent PRs.
Quoting https://github.com/opencontainers/runc/runs/2787163520?check_suite_focus=true:
The test case was added in commit 4438eaa, PR #2391.
This
sh: can't create /dev/null: Operation not permitted
means somewhere duringrunc update
the device access list might become empty for some time.May be related to recent PR #2994 (although I do not see how). Definitely not related to PR #2986 as we have cgroup v1 here.
The text was updated successfully, but these errors were encountered: