-
Notifications
You must be signed in to change notification settings - Fork 196
ci: Refer to stable-2.1 branch on stable-2.1 branch #3504
ci: Refer to stable-2.1 branch on stable-2.1 branch #3504
Conversation
/test |
fc23172
to
adeda4d
Compare
/test |
adeda4d
to
150e3b0
Compare
/test |
/test-fedora |
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.
It looks like this is not documented in the release process https://github.com/kata-containers/kata-containers/blob/main/docs/Release-Process.md. Would it make sense to add it there?
It'd make sense to, somehow, automate it, in the same way we did for the kata-deploy versions. |
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.
@fidencio nit: extra slash in readme
README.md
Outdated
@@ -160,7 +159,7 @@ You need to install the following to run Kata Containers tests: | |||
- [golang](https://golang.org/dl) | |||
|
|||
To view the versions of go known to work, see the `golang` entry in the | |||
[versions database](https://github.com/kata-containers/kata-containers/blob/main/versions.yaml). | |||
[versions database](https://github.com/kata-containers/kata-containers/blob/stable-2.1//versions.yaml). |
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.
@fidencio there is an extra forward slash in this line
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.
Thanks, fixed!
150e3b0
to
cb01516
Compare
/test |
1 similar comment
/test |
@fidencio, thanks, why does this last merge commit is needed? |
As we still didn't get CRI-O unit tests to run against shimv2, we removed those from our tree as part 816aee4. However, we left some documentation behind and that will break the static check. Fixes: kata-containers#3505 Backport of kata-containers#3506 Signed-off-by: Fabiano Fidêncio <[email protected]>
This commit forces all the checks and references to point to stable-2.1 branch rather than pointing to `main`. This will guarantee that changes done on `main` won't affect the testing of this specific branch. Fixes: kata-containers#3507 Signed-off-by: Fabiano Fidêncio <[email protected]>
73f85c4
to
f597ebe
Compare
I must admit I don't understand why GitHub doesn't understand my rebase atop of That's the reason why we ended up with a merge commit. |
D'uh! I opened this PR against |
/test |
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.
LGTM
@wainersm, since we merged the ability to use a cached kernel I've noticed failures like:
I would like to believe those are not related, I really do, but I think those can be. This comes from http://jenkins.katacontainers.io/job/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/251/ |
/test |
I had to close and re-open because some checks were stuck. |
Still about this, @jcvenegas, @likebreath, have you faced this before? |
This commit forces all the checks and references to point to stable-2.1
branch rather than pointing to
main
. This will guarantee that changesdone on
main
won't affect the testing of this specific branch.Signed-off-by: Fabiano Fidêncio [email protected]