Brian Goff 27ba755f70 Fix racey TestHealthKillContainer ... Before this change if you assume that things work the way the test expects them to (it does not, but lets assume for now) we aren't really testing anything because we are testing that a container is healthy before and after we send a signal. This will give false positives even if there is a bug in the underlying code. Sending a signal can take any amount of time to cause a container to exit or to trigger healthchecks to stop or whatever. Now lets remove the assumption that things are working as expected, because they are not. In this case, `top` (which is what is running in the container) is actually exiting when it receives `USR1`. This totally invalidates the test. We need more control and knowledge as to what is happening in the container to properly test this. This change introduces a custom script which traps `USR1` and flips the health status each time the signal is received. We then send the signal twice so that we know the change has occurred and check that the value has flipped so that we know the change has actually occurred. Signed-off-by: Brian Goff <cpuguy83@gmail.com>		2021-10-21 19:27:07 +00:00
..
build
config
container	Fix racey TestHealthKillContainer	2021-10-21 19:27:07 +00:00
daemon
distribution
image
internal
network
plugin
secret
service
session
system
testdata/https
volume
doc.go