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
test: 5.4 CI job #15765
test: 5.4 CI job #15765
Conversation
b4b82d3
to
cba0533
Compare
Since the goal of the 5.4 CI job is only to catch complexity issues, other test suites are skipped. They are not expected to help us catch new complexity issues compared to K8sVerifier and K8sDatapathConfig. Signed-off-by: Paul Chaignon <paul@cilium.io>
test-me-please |
test-1.19-5.4 |
The only failing test is in k8s-1.16-kernel-netnext and is due to known flake #15455. The team reviews not yet covered are cilium/policy, cilium/proxy, and cilium/hubble. They are requested only due to commit fbba867 which skips a bunch of tests on the 5.4 pipeline. I don't think they are actually needed because cilium/ci-structure's review should be sufficient for that commit. There are also already four other approving reviews. Marking as ready to merge. |
This pull request extends our end-to-end tests to support the new 5.4 CI job, aimed at catching complexity issues. At a high level, the commits implements the following.
RunsOnNetNextOr419Kernel
toRunsOn419OrLaterKernel
as it will include 5.4.RunsOn54Kernel
helper function.Please see commit descriptions for details.