-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
CI: multi kernel DP conformance #21465
Conversation
98b5c70
to
aaa7bf1
Compare
This pull request has been automatically marked as stale because it |
f02ab59
to
79b3785
Compare
Currently, the 4.19 is excluded for now, as it doesn't use kvm-clock as a time source which is causing some stability issues. Signed-off-by: Martynas Pumputis <m@lambda.lt>
79b3785
to
28b11c4
Compare
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, one minor question about the timeout
fail-fast: false | ||
matrix: | ||
kernel: ['5.4', '5.10', '5.15', 'bpf-next'] | ||
timeout-minutes: 120 |
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.
Doesn't look like 45 x 4
? Was 45
too much?
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.
I mean that GH can run this sequentially, right?
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.
These will be run in parallel. I set to 120min to catch some stability issues (TL;DR some VMs are still not using kvm-clock as a time source).
The CI has previously passed - https://github.com/cilium/cilium/actions/runs/3370650528/jobs/5591823167