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.

Sign up for GitHub

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

Jump to bottom

CI: Reevaluate use of Ubuntu #15337

Closed
edsantiago opened this issue Aug 16, 2022 · 5 comments
Closed

CI: Reevaluate use of Ubuntu #15337

edsantiago opened this issue Aug 16, 2022 · 5 comments
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue

Comments

@edsantiago
Copy link
Member

There's a whole swath of tests being skipped on Ubuntu:

AIUI the point of using Ubuntu in CI is testing runc + cgroups v1. The point of testing runc + cgroups v1 is because that's what RHEL8 has, and not that many of us enjoy the panic-scrambles when RHEL8 gating tests fail because we haven't actually been testing very much.

This is a place for us to discuss how to improve our coverage.
@rhatdan
Copy link
Member

rhatdan commented Aug 16, 2022

I would also add that one reason to run tests on Ubuntu, is that it is the most popular Linux distribution.

We could add RHEL8/Centos 8 Stream Tests for just system tests. The reason we have avoided them is because there could be/will be features that will not work on them that we don't want to break upstream.

@rhatdan
Copy link
Member

rhatdan commented Aug 16, 2022

BTW, Having a platform that does test the limited AppArmor support versus SELinux is also a reason to run on Ubuntu.

edsantiago added a commit to edsantiago/libpod that referenced this issue Aug 16, 2022
@edsantiago
system tests: fix broken runc test
06b3a4c 
Followup to containers#14613, which was never actually tested until this
week in RHEL8 gating tests (see issue containers#15337).

 * add missing backslash in '|' expression
 * allow extra text after error (e.g., "invalid argument")

No way to test this until it makes its way into RHEL8,
so, fingers crossed.

Signed-off-by: Ed Santiago <[email protected]>
@edsantiago edsantiago mentioned this issue Aug 16, 2022
Merged
@edsantiago edsantiago mentioned this issue Aug 31, 2022
Closed
@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@edsantiago
Copy link
Member Author

We abandoned ubuntu testing over two months ago.

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 4, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@edsantiago @rhatdan