Skip to content
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

cgroup2: CI failure (bad rebase #2165): process_linux.go:297: applying cgroup configuration for process caused "mountpoint for not found" #2175

Closed
AkihiroSuda opened this issue Dec 6, 2019 · 2 comments

Comments

@AkihiroSuda
Copy link
Member

This has started failing with process_linux.go:297: applying cgroup configuration for process caused "mountpoint for not found". If this was intended to fail until we get cgroupv2 working completely, the test should've been marked as fail-able...

Originally posted by @cyphar in #2165 (comment)

@AkihiroSuda AkihiroSuda changed the title CI failure (bad rebase #2165): process_linux.go:297: applying cgroup configuration for process caused "mountpoint for not found" cgroup2: CI failure (bad rebase #2165): process_linux.go:297: applying cgroup configuration for process caused "mountpoint for not found" Dec 6, 2019
@AkihiroSuda
Copy link
Member Author

#2169 fixes the issue.

AkihiroSuda added a commit to AkihiroSuda/runc that referenced this issue Dec 31, 2019
…#2169 gets merged)

CI seems to have been broken due to some bad rebase during merging multiple cgroup2 PRs: opencontainers#2175

The failure is being fixed in opencontainers#2169, but still waiting for review.

This PR updates .travis.yml to ignore the failure as a workaround until opencontainers#2169 gets merged.

This PR can be closed if opencontainers#2169 can get merged right now (and that's even better).

Signed-off-by: Akihiro Suda <[email protected]>
@AkihiroSuda
Copy link
Member Author

#2169 is still waiting fore review.

Opened #2195 as a workaround until #2169 gets merged.
#2195 doesn't need to be merged if #2169 can be merged right now.

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

No branches or pull requests

1 participant