Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Test component health flake #9936

Closed
medyagh opened this issue Dec 11, 2020 · 1 comment · Fixed by #10424
Closed

Test component health flake #9936

medyagh opened this issue Dec 11, 2020 · 1 comment · Fixed by #10424
Assignees
@prezha
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@medyagh
Copy link
Member

medyagh commented Dec 11, 2020 •
edited
Loading

example docker driver GH action:

https://github.com/kubernetes/minikube/runs/1540063530

https://storage.googleapis.com/minikube-builds/logs/9933/f3be305/none_Linux.html#fail_TestFunctional%2fparallel%2fComponentHealth

passrate report

-------------------------------------------------
docker_Linux      | 2020-12-07 | 100% | 11 of 11
docker_Linux      | 2020-12-08 | 100% | 12 of 12
docker_Linux      | 2020-12-09 | 100% | 11 of 11
docker_Linux      | 2020-12-10 | 100% | 11 of 11
docker_Linux      | 2020-12-11 | 100% | 6 of 6
-------------------------------------------------
HyperKit_macOS    | 2020-12-08 | 100% | 4 of 4
HyperKit_macOS    | 2020-12-09 | 100% | 11 of 11
HyperKit_macOS    | 2020-12-10 | 100% | 11 of 11
HyperKit_macOS    | 2020-12-11 | 100% | 7 of 7
-------------------------------------------------
Hyper-V_Windows   | 2020-12-10 |   0% | 0 of 1
-------------------------------------------------
KVM_Linux         | 2020-12-07 |  58% | 7 of 12
KVM_Linux         | 2020-12-08 |  83% | 10 of 12
KVM_Linux         | 2020-12-09 |  33% | 4 of 12
KVM_Linux         | 2020-12-10 |  73% | 8 of 11
KVM_Linux         | 2020-12-11 |  38% | 3 of 8
-------------------------------------------------
none_Linux        | 2020-12-07 | 100% | 12 of 12
none_Linux        | 2020-12-08 | 100% | 12 of 12
none_Linux        | 2020-12-09 |  91% | 10 of 11
none_Linux        | 2020-12-10 |  69% | 9 of 13
none_Linux        | 2020-12-11 |  86% | 6 of 7
-------------------------------------------------
VirtualBox_Linux  | 2020-12-07 | 100% | 11 of 11
VirtualBox_Linux  | 2020-12-08 | 100% | 11 of 11
VirtualBox_Linux  | 2020-12-09 | 100% | 8 of 8
VirtualBox_Linux  | 2020-12-11 | 100% | 2 of 2
-------------------------------------------------
z__ALL__          | 2020-12-07 |  89% | 41 of 46
z__ALL__          | 2020-12-08 |  96% | 49 of 51
z__ALL__          | 2020-12-09 |  83% | 44 of 53
z__ALL__          | 2020-12-10 |  83% | 39 of 47
z__ALL__          | 2020-12-11 |  80% | 24 of 30
-------------------------------------------------
@medyagh medyagh added kind/flake Categorizes issue or PR as related to a flaky test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Dec 11, 2020
@prezha
Copy link
Contributor

prezha commented Dec 12, 2020

/assign

@prezha prezha mentioned this issue Dec 12, 2020
Closed
@priyawadhwa priyawadhwa added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Feb 3, 2021
@prezha prezha mentioned this issue Feb 9, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@prezha prezha

Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add new extra component to --wait=all to validate a healthy cluster prezha/minikube
3 participants
@medyagh @prezha @priyawadhwa