-
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
reboot windows machines after every test #12667
reboot windows machines after every test #12667
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sharifelgamal The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/ok-to-test |
kvm2 driver with docker runtime
Times for minikube start: 49.1s 46.8s 47.5s 47.7s 47.2s Times for minikube ingress: 39.8s 32.8s 33.3s 31.3s 31.4s docker driver with docker runtime
Times for minikube start: 22.9s 21.8s 21.2s 22.6s 21.9s Times for minikube ingress: 35.4s 35.4s 27.9s 30.4s 34.5s docker driver with containerd runtime
Times for minikube ingress: 32.9s 32.4s 37.9s 42.4s 36.4s Times for minikube start: 31.6s 43.3s 42.6s 26.2s 40.9s |
These are the flake rates of all failed tests.
To see the flake rates of all tests by environment, click here. |
We're having some issues with zombie processes holding on to file locks in our integration testing workspaces so I'm going to try just rebooting machines as often as possible.
Also let's lower the frequency of the cron to every 30 minutes.