Skip to content

TestErrorSpam: Restarting the docker service may improve performance #7601

Closed
@medyagh

Description

@medyagh

as seen in
https://storage.googleapis.com/minikube-builds/logs/7586/d512c84/Docker_Linux.html#fail_TestErrorSpam

=== RUN   TestErrorSpam
=== PAUSE TestErrorSpam
=== CONT  TestErrorSpam
--- FAIL: TestErrorSpam (168.88s)
error_spam_test.go:42: (dbg) Run:  out/minikube-linux-amd64 start -p nospam-20200410T153613.393267403-15978 -n=1 --memory=2250 --wait=false --driver=docker 
error_spam_test.go:42: (dbg) Done: out/minikube-linux-amd64 start -p nospam-20200410T153613.393267403-15978 -n=1 --memory=2250 --wait=false --driver=docker : (2m15.474942738s)
error_spam_test.go:57: unexpected stderr line: "* Restarting the docker service may improve performance."
error_spam_test.go:57: unexpected stderr line: "stdout:"
error_spam_test.go:57: unexpected stderr line: "serviceaccount/storage-provisioner unchanged"
error_spam_test.go:57: unexpected stderr line: "clusterrolebinding.rbac.authorization.k8s.io/storage-provisioner unchanged"
error_spam_test.go:57: unexpected stderr line: "stderr:"
error_spam_test.go:49: unexpected error log in stderr: "Error from server (ServerTimeout): error when creating \"/etc/kubernetes/addons/storage-provisioner.yaml\": No API token found for service account \"storage-provisioner\", retry after the token is automatically created and added to the service account"
error_spam_test.go:57: unexpected stderr line: "]"
error_spam_test.go:69: *** TestErrorSpam FAILED at 2020-04-10 15:38:28.868492686 -0700 PDT m=+725.487531520
helpers.go:198: (dbg) Run:  out/minikube-linux-amd64 status --format={{.Host}} -p nospam-20200410T153613.393267403-15978
helpers.go:198: (dbg) Done: out/minikube-linux-amd64 status --format={{.Host}} -p nospam-20200410T153613.393267403-15978: (1.579189399s)

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions