2018-07-04 10:26:32 -07:00
|
|
|
CI_BUILD_START=$(date +%s)
|
|
|
|
|
export CI_BUILD_START
|
2019-01-31 11:56:15 -08:00
|
|
|
|
2019-02-06 13:39:19 -08:00
|
|
|
#
|
|
|
|
|
# Kill any running docker containers, which are potentially left over from the
|
|
|
|
|
# previous CI job
|
|
|
|
|
#
|
|
|
|
|
(
|
|
|
|
|
containers=$(docker ps -q)
|
2019-02-07 08:18:48 -08:00
|
|
|
if [[ $(hostname) != metrics-solana-com && -n $containers ]]; then
|
|
|
|
|
echo "+++ Killing stale docker containers"
|
2019-02-06 13:39:19 -08:00
|
|
|
docker ps
|
|
|
|
|
|
|
|
|
|
# shellcheck disable=SC2086 # Don't want to double quote $containers
|
|
|
|
|
docker kill $containers
|
|
|
|
|
fi
|
|
|
|
|
)
|
|
|
|
|
|
2019-01-31 11:56:15 -08:00
|
|
|
# Processes from previously aborted CI jobs seem to loiter, unclear why as one
|
|
|
|
|
# would expect the buildkite-agent to clean up all child processes of the
|
|
|
|
|
# aborted CI job.
|
|
|
|
|
# But as a workaround for now manually kill some known loiterers. These
|
|
|
|
|
# processes will all have the `init` process as their PPID:
|
|
|
|
|
(
|
|
|
|
|
victims=
|
|
|
|
|
for name in bash cargo docker solana; do
|
|
|
|
|
victims="$victims $(pgrep -u "$(id -u)" -P 1 -d \ $name)"
|
|
|
|
|
done
|
|
|
|
|
for victim in $victims; do
|
|
|
|
|
echo "Killing pid $victim"
|
|
|
|
|
kill -9 "$victim" || true
|
|
|
|
|
done
|
|
|
|
|
)
|
