-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Cirrus: Support testing with F31 #3901
Conversation
LGTM. The F31 packages will have to be tested with crun, not runc. Or we need to disable cgroupsV2. |
☔ The latest upstream changes (presumably #3728) made this pull request unmergeable. Please resolve the merge conflicts. |
Thanks, I half-guessed at this. I'm thinking we can drop the cgroupsv2/crun task, since having F31 in the mix will satisfy these neeeds. @giuseppe is that right, or is there reason to continue testing either on F30? |
ewww, errr, crap |
66936df
to
d578002
Compare
F31 VM setup packaging failures:
|
All: Earliest working F31 cache-image build is (yes |
☔ The latest upstream changes (presumably #3817) made this pull request unmergeable. Please resolve the merge conflicts. |
Signed-off-by: Chris Evich <[email protected]>
The default scheduler is BFQ but integration tests run into https://bugzilla.redhat.com/show_bug.cgi?id=1767539 aka https://bugzilla.kernel.org/show_bug.cgi?id=205447 Using the deadline elevator as a workaround. Signed-off-by: Chris Evich <[email protected]>
In some distributions it's possible to have both runc and crun installed and/or for podman to be confused about which to use. In these instances, force the decision by adding `OCI_RUNTIME=/usr/bin/crun` into `/etc/environment`. Also in-place modify libpod.conf to use 'crun' instead of 'runc' Signed-off-by: Chris Evich <[email protected]>
Signed-off-by: Chris Evich <[email protected]>
Signed-off-by: Chris Evich <[email protected]>
Signed-off-by: Chris Evich <[email protected]>
Signed-off-by: Chris Evich <[email protected]>
Sometime between 10th and 23rd of Feb. 2020, the behavior of crun changed. Upon consulting with Giuseppe, the podman run tests for `device-read-*` and `device-write-*` do not depend on the container output for success, only the exit code. Add a comment and conditional regarding this in case of cgroupsv2. Also noted that these tests will likely require future refactoring/simplification. Signed-off-by: Chris Evich <[email protected]>
Recommended as part of: containers#5004 and containers/crun#230 Signed-off-by: Chris Evich <[email protected]>
It's possible/likely the container image for the test will need to be pulled as part of the `run` command. Due to the way BATS handles output, messages regarding image-pull could be misinterpreted as the container's CID. Force the CID to be obtained by only the last line of output. Signed-off-by: Chris Evich <[email protected]>
Signed-off-by: Chris Evich <[email protected]>
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: baude, cevich The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
LGTM |
/lgtm |
Add F31 + Drop F29
Depends on: #3754 #4028 #4028 #4154 #4222 #4825
Fixes #5285
Fixes #3447
Signed-off-by: Chris Evich [email protected]