-
Notifications
You must be signed in to change notification settings - Fork 16
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
Unblock CI #219
Unblock CI #219
Conversation
The integration tests use Python 3.8 / ubuntu 20.04. The problem is that k8s-snap tests use type specifiers that require Python 3.10. For this reason, we'll switch to Python 3.10 / ubuntu 22.04.
BenchmarkResults
Current status
|
This simplifies the gh workflows and also applies the Docker iptables workaround.
76ad142
to
b1cdfa7
Compare
k8s-snap switched to self-hosted CI runners as the default Github ones didn't have enough resources. We'll update the k8s-dqlite CI job to use self-hosted runners as well when running k8s-snap integration tests.
7e18101
to
32d9896
Compare
The CI is hitting this error:
We'll also need the following PR to unlock the tests: #212 LE: picked just the changes that remove the failing checks. |
The e2e tests are currently failing because of this k8s-dqlite error: k8s.k8s-dqlite[1947]: time="2025-01-09T15:00:22Z" level=error msg="error while range on /registry/clusterroles/system:aggregate-to-view : unexpected limit: want 0, got 1" A separate PR is removing this check: #212 That being considered, we'll apply this change here to unblock the CI.
Got a new error:
|
I see |
ohh, my bad. thanks! |
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, thanks so much Lucian!
Thank you for making K8s-dqlite better
Please reference the issue this PR is fixing, or provide a description of the problem addressed.
Also verify you have: