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

tests/int: skip "update memory vs CheckBeforeUpdate" on EL9 #4455

Merged
merged 1 commit into from
Oct 18, 2024

Conversation

kolyshkin
Copy link
Contributor

This test case is frequently hanging recently. Might be caused by a recent kernel update from 5.14.0-427.33.1.el9_4.x86_64 to 5.14.0-427.37.1.el9_4.x86_64.

Could not reproduce locally.

Let's skip it for now.

Fixes: #4454

@kolyshkin kolyshkin mentioned this pull request Oct 18, 2024
@kolyshkin
Copy link
Contributor Author

OK, it's not this test, it's probably the next one.

@kolyshkin kolyshkin changed the title tests/int: don't run "update paused container" on EL9 tests/int: skip "update memory vs CheckBeforeUpdate" on EL9 Oct 18, 2024
This test case is frequently hanging recently. Might be caused
by a recent kernel update from 5.14.0-427.33.1.el9_4.x86_64 to
5.14.0-427.37.1.el9_4.x86_64.

Could not reproduce locally.

Let's skip it for now.

Signed-off-by: Kir Kolyshkin <[email protected]>
@kolyshkin kolyshkin marked this pull request as ready for review October 18, 2024 04:40
@kolyshkin
Copy link
Contributor Author

close/reopen to kick CI

@kolyshkin kolyshkin closed this Oct 18, 2024
@kolyshkin kolyshkin reopened this Oct 18, 2024
@rata
Copy link
Member

rata commented Oct 18, 2024

This seems to fix almalinux-9, but ubuntu failed with:

=== RUN   TestSeccompPermitWriteConditional
    seccomp_test.go:153: unexpected error: unable to start container process: unable to start init: fork/exec /proc/self/fd/7: permission denied
--- FAIL: TestSeccompPermitWriteConditional (0.13s)

which doesn't seem like a flake :-/

@rata
Copy link
Member

rata commented Oct 18, 2024

Oh, that is fixed by #4452 :)

Copy link
Member

@rata rata left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

It would be great to report the issue to upstream, but we need to have a working CI meanwhile. Do you know where to report it? Maybe some redhat thingy? Or just fedora?

@lifubang lifubang merged commit d1b0ae6 into opencontainers:main Oct 18, 2024
79 of 80 checks passed
@kolyshkin
Copy link
Contributor Author

OK, ran it a few times and it looks like it's working. The issue is something about OOM killer and for some reason it's only revealing itself on Cirrus CI. I will debug it further but for now we should just skip the test.

@kolyshkin
Copy link
Contributor Author

Do you know where to report it? Maybe some redhat thingy? Or just fedora?

If we're still talking about the hang, I need more time to look into it. Maybe this is something about Google cloud instance being used, or some Cirrus CI, or something else, but I can't repro it locally so probably it's not about Alma Linux 9 or the new kernel per se.

In Cirrus CI, you can have a terminal to debug, and I used that; the problem is soon after the tests hang, terminal hangs as well. I will keep looking into it.

@rata
Copy link
Member

rata commented Oct 21, 2024

Makes sense. Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CI fails on almalinux 9
3 participants