I start to run e2e tests:
$ $GOPATH/bin/kubetest --test -v --test_args=--ginkgo.focus=.*Rescheduler.*
I then ^C to cancel running tests.
kubetest exits and returns me to the console, but hack/ginkgo-e2e.sh and subprocesses (like ginkgo) continue to run.
The same issue exists if I interrupt kubetest --up.
maybe related to https://github.com/kubernetes/kubernetes/issues/39041
This still doesn't work
I can try this one 馃槃
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
any progress on this?
@ixdy I did not have time and it gets lost in my items. However, I can come back to this. I have some questions regarding kubetest, who is the best contact to clarify?
i apologize for this taking too much time
/remove-lifecycle stale
almost there. fighting to spin the cluster in my local machine
Most helpful comment
I can try this one 馃槃