We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Terratest results failing, and round-robin tests failing
extensions.go:235: killing Instance: k3d-test-gslb2:k8gb-test-bmgcyi TestFullFailover 2022-01-14T21:56:28+02:00 client.go:42: Configuring Kubernetes client using config file /home/namai/.kube/config with context k3d-test-gslb2 extensions.go:235: killing Instance: k3d-test-gslb1:k8gb-test-w0g9tt TestFullFailover 2022-01-14T21:56:28+02:00 client.go:42: Configuring Kubernetes client using config file /home/namai/.kube/config with context k3d-test-gslb1 --- FAIL: TestFullFailover (441.28s) --- PASS: TestFullFailover/failover_on_two_concurrent_clusters_with_podinfo_running (3.04s) --- FAIL: TestFullFailover/kill_podinfo_on_the_second_cluster (105.48s) --- PASS: TestFullFailover/kill_podinfo_on_the_first_cluster (0.20s) --- FAIL: TestFullFailover/start_podinfo_on_the_second_cluster (109.56s) --- FAIL: TestFullFailover/start_podinfo_on_the_first_cluster (106.90s) FAIL exit status 1 FAIL k8gbterratest/test 441.297s
What steps I should take to find the cause? OS: Debian 11 "Bullseye" Go 17.6.1 Docker 20.10.5
Originally posted by @AugustasV in #828 (comment)
The text was updated successfully, but these errors were encountered:
@kuritka probably this issue could be closed because those error messages are not appearing anymore.
Sorry, something went wrong.
@AugustasV , sure, closing. This is something else.
No branches or pull requests
Terratest results failing, and round-robin tests failing
What steps I should take to find the cause?
OS: Debian 11 "Bullseye"
Go 17.6.1
Docker 20.10.5
Originally posted by @AugustasV in #828 (comment)
The text was updated successfully, but these errors were encountered: