-
Notifications
You must be signed in to change notification settings - Fork 4.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
test: allow running functional tests for different k8s versions #18564
base: master
Are you sure you want to change the base?
test: allow running functional tests for different k8s versions #18564
Conversation
Hi @ComradeProgrammer. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Can one of the admins verify this patch? |
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.
@ComradeProgrammer can we make it in a way that the TestName will show different when it fails ?
I rather we have a new test like this
func TestFunctional(t *testing.T) {
k8sversion= DEFAULT_ONE
///. the current test
commonFunctiona() ...
}
func TestFunctionalNewestKuberentes(t *testing.T) {
k8sversion= NEWEST ONES
// here it should call the commonTest
commonFunctiona() ...
}
// generic common test that wilill be called by others
func commonFunctionalt *testing.T) {
}
2d03356
to
9279e98
Compare
Revised. Now they are named Versionxxx is added so that we don't need to change anything if we want to run a specified functional test on an active minikube cluster( tests for newest version won't be triggered when we use something like |
9279e98
to
224bcb6
Compare
224bcb6
to
8167a9a
Compare
/ok-to-test |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
8167a9a
to
981083d
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
24a9e9e
to
4722894
Compare
This comment has been minimized.
This comment has been minimized.
1e215c5
to
f4e30a8
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
39a928e
to
7070dbd
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
7070dbd
to
b139639
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ComradeProgrammer The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This comment has been minimized.
This comment has been minimized.
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Co-authored-by: Steven Powell <[email protected]>
266b4c3
to
7b31a43
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.
You have lint issues, could you run gofmt -w -s .
/ok-to-test |
lets fix the lint and rebase |
kvm2 driver with docker runtime
Times for minikube start: 50.0s 52.0s 50.7s 50.7s 52.4s Times for minikube ingress: 19.0s 15.5s 19.5s 16.0s 16.0s docker driver with docker runtime
Times for minikube start: 24.5s 24.0s 25.1s 24.0s 20.8s Times for minikube (PR 18564) ingress: 12.8s 12.3s 12.8s 12.8s 12.3s docker driver with containerd runtime
Times for minikube start: 22.8s 20.1s 22.8s 23.1s 19.7s Times for minikube ingress: 38.8s 38.8s 38.8s 22.8s 38.8s |
Here are the number of top 10 failed tests in each environments with lowest flake rate.
Besides the following environments also have failed tests:
To see the flake rates of all tests by environment, click here. |
FIX #18508
test: allow running functional tests for different k8s versions
It also fix a small bug in minikube tunnel. Now we also check the machine name stored in the tunnel.json when preventing establishing duplicated tunnel.
Before: functional test can only be run for default specified k8s version
After:
Here are the example outputs(most tests are disabled for simplification)