-
Notifications
You must be signed in to change notification settings - Fork 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
tests/cri-containerd: split between cri-containerd and crictl suites #8096
base: main
Are you sure you want to change the base?
Conversation
12dffe6
to
d94d30c
Compare
Hi @fidencio !
Once upon a time PR #8061, that @beraldoleal asked me to help understand why some CI jobs failed. I took look at https://github.com/kata-containers/kata-containers/actions/runs/6356069723/job/17266102296?pr=8061 first, when I realized that our
So my goal is to split those two types of tests in different suites to easy the interpretation of the logs when the CI fail. The tests 2) ( Let me know if I'm missing something and/or this is an unwanted/worthless split. |
ah, and the tests 2) ( |
Aha, okay, it makes sense. I'd just not name it as cri-containerd-integration :-) |
hmm.. what do you suggest? Keep containerd's cri-integration tests called |
run-cri-containerd (lts, qemu) is also failing locally and I still don´t know why. |
d94d30c
to
df1633a
Compare
Fixed. Added an instruction to pull the pause image before creating the pod. |
df1633a
to
57f78c6
Compare
Re-done my initial PR to move the crictl tests to its own suite (guess what, named Once CI passing I should be working on:
|
911c12c
to
9e05f86
Compare
9e05f86
to
be5b9f4
Compare
be5b9f4
to
f870fb5
Compare
@fidencio this PR is ready to review. The three commits that convert to bats I should squash after the reviews (keeping them separated to ease the reviewer's life). |
yeah, my tentative to build a house in ascii didn't work out.... |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, one minor comment...
Created the tests/integration/cri-containerd/lib.sh file to host code that can be shared with other tests suites. The original code wasn't touched, it just moved of place. In preparation to create the crictl suite of tests. Fixes kata-containers#8160 Signed-off-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
The tests/integration/cri-containerd currently runs the containerd's cri-integration tests plus a couple of kata's specific tests using crictl. Splited in two suites of tests: * cri-containerd - keep running the containerd's cri-integration tests * crictl - new home for crictl based tests The code is essentially a copy of * cri-containerd/integration-tests.sh -> crictl/run_tests.sh * cri-containerd/gha-run.sh -> crictl/gha-run.sh On crictl/run_tests.sh, `testContainerStart()` was added a handler to pull the pause image before creating the pod. Fixes kata-containers#8160 Signed-off-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
Re-implemented the tests to use the bats framework. Fixes kata-containers#8160 Signed-off-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
Added a new workflow to run the tests/integration/crictl suite of tests with same containerd/hypervisor matrix as cri-containerd workflow. Important: at this point the workflow won't fail due to failing tests. Fixes kata-containers#8160 Signed-off-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
f870fb5
to
f81722b
Compare
Rebase this to main, added a header to |
@wainersm - Do we still want to get this in? I think it needs a rebase and re-test and then we can have another attempt? |
This split the cri-containerd in two suites of tests:
Then the crictl tests were convert to use the bats framework. I didn't want to improve the tests, depict many opportunities, so I tried to keep the original code and logic intact as much as possible. In the future, when we start pulling tests from CCv0 I think it will be the right time for improvements.
A github workflow was created to run the crictl suite of tests. The workflow won't fail due to failures on tests, because I will be able to fully test the tests on CI after the workflow is merged (right?) and then I don't want a broken workflow blocking unrelated pull requests.
Fixes #8160