5290aac66f
Sometimes the container runtime detects the exiting PID 1 very quickly and shuts down the entire container while the `killall` process is still running. When this happens, we see it as exit code 137 (SIGKILL). This never failed for me in Kind locally, but fails pretty often in CI (probably due to timing differences). Signed-off-by: Matt Moyer <moyerm@vmware.com> |
||
---|---|---|
.. | ||
cli_test.go | ||
client_test.go | ||
concierge_api_serving_certs_test.go | ||
concierge_availability_test.go | ||
concierge_credentialissuerconfig_test.go | ||
concierge_credentialrequest_test.go | ||
concierge_kubecertagent_test.go | ||
concierge_kubectl_test.go | ||
e2e_test.go | ||
kube_api_discovery_test.go | ||
kubeclient_test.go | ||
supervisor_discovery_test.go | ||
supervisor_healthz_test.go | ||
supervisor_login_test.go | ||
supervisor_secrets_test.go | ||
supervisor_storage_garbage_collection_test.go | ||
supervisor_storage_test.go | ||
supervisor_upstream_test.go |