ContainerImage.Pinniped/test
Matt Moyer 5290aac66f
Adjust "/bin/killall sleep" in new test to be less flaky in CI.
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>
2021-04-22 14:51:55 -05:00
..
cluster_capabilities Update copyright to reference Pinniped contributors 2020-09-16 10:05:51 -04:00
deploy/dex Move our main image references to the VMware Harbor registry. 2020-12-17 17:51:09 -06:00
integration Adjust "/bin/killall sleep" in new test to be less flaky in CI. 2021-04-22 14:51:55 -05:00
library test/integration: add test helper to avoid race conditions 2021-01-14 10:19:35 -05:00