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.

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

TestErrorSpam: cache_images.go: error getting status for <cluster>: Error: No such object #7760

Closed
medyagh opened this issue Apr 18, 2020 · 4 comments · Fixed by #7872
Closed
Assignees
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. 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.
Milestone

Comments

@medyagh
Copy link
Member

medyagh commented Apr 18, 2020

in this this it is very clear that Test is unhappy about Error in another Test.
https://storage.googleapis.com/minikube-builds/logs/7752/21ad12f/Docker_Linux.html#fail_TestErrorSpam

error_spam_test.go:61: unexpected error log: "E0418 01:01:09.373611   32170 cache_images.go:196] error getting status for docker-flags-20200418T005800-24883: state: unknown state"
error_spam_test.go:61: unexpected error log: "E0418 01:01:11.791557   32170 cache_images.go:196] error getting status for pause-20200418T005800-24883: state: \"docker inspect -f {{.State.Status}} pause-20200418T005800-24883\" failed: exit status 1: Error: No such object: pause-20200418T005800-24883"

I believe it is better we put this test in our Funcitional Test and make sure no other VM is running while this test finishes.
so there dont be any talking over this test.

@medyagh medyagh changed the title TestErrorSpam: fails on other tests talking over the Test TestErrorSpam: fails for the wrong reason ( tests talking over each other) Apr 18, 2020
@medyagh medyagh added kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. kind/flake Categorizes issue or PR as related to a flaky test. labels Apr 18, 2020
@medyagh medyagh added this to the v1.10.0 milestone Apr 18, 2020
@medyagh medyagh added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Apr 18, 2020
@tstromberg
Copy link
Contributor

I believe you are misinterpreting the result. This test already runs in serial. I believe this is showing
real errors because of state changes related to other clusters. We should either whitelist these errors, or turn them into warnings.

@tstromberg tstromberg changed the title TestErrorSpam: fails for the wrong reason ( tests talking over each other) TestErrorSpam: cache_images.go: error getting status for <cluster>: Error: No such object Apr 22, 2020
@tstromberg tstromberg assigned tstromberg and unassigned tstromberg Apr 22, 2020
@priyawadhwa priyawadhwa reopened this May 5, 2020
@priyawadhwa
Copy link

Reopening as I just saw this error on KVM_Linux in #8010

test logs

error_spam_test.go:94: minikube stderr:
! Unable to verify SSH connectivity: dial tcp 192.168.99.249:22: i/o timeout. Will retry...
! Unable to verify SSH connectivity: dial tcp 192.168.99.249:22: i/o timeout. Will retry...
error_spam_test.go:96: *** TestErrorSpam FAILED at 2020-05-05 19:51:03.612317896 +0000 UTC m=+1903.983929985

@tstromberg
Copy link
Contributor

@priyawadhwa - that seems to be an unrelated issue.

@tstromberg
Copy link
Contributor

Opened a new issue: #8011

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. 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.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants