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
As a consequence there is no possibility of debugging test failures, IIRC the logs should be obtained before we are tearing down the cluster, but when this option was added , it got added to the Up() hook https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-gce-conformance-latest-kubetest2/1845682784069226496
Up()
fb21a08
It seems the AWS one logs correctly
https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-cloud-provider-aws-e2e-kubetest2/1845768599910748160
The text was updated successfully, but these errors were encountered:
/cc @BenTheElder @krzyzacy
Sorry, something went wrong.
Suggestions from @soltysh seems the best one, moving the dump of the logs to the Down() hook
Down()
https://github.com/kubernetes-sigs/kubetest2/blob/master/kubetest2-gce/deployer/down.go#L28
Successfully merging a pull request may close this issue.
As a consequence there is no possibility of debugging test failures, IIRC the logs should be obtained before we are tearing down the cluster, but when this option was added , it got added to the
Up()
hook https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-gce-conformance-latest-kubetest2/1845682784069226496fb21a08
It seems the AWS one logs correctly
https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-cloud-provider-aws-e2e-kubetest2/1845768599910748160
The text was updated successfully, but these errors were encountered: