From 64b18a0b9145301b32989b714b1523af41bae1ca Mon Sep 17 00:00:00 2001 From: Nicholas Pettas Date: Fri, 13 Dec 2024 16:05:11 -0800 Subject: [PATCH] fix missing docker image --- .buildkite/hooks/post-checkout | 34 ----------------------------- .buildkite/scripts/build-bench.sh | 13 ----------- .buildkite/scripts/build-stable.sh | 35 ------------------------------ 3 files changed, 82 deletions(-) diff --git a/.buildkite/hooks/post-checkout b/.buildkite/hooks/post-checkout index 873b3f9ec175a5..54779337e32300 100644 --- a/.buildkite/hooks/post-checkout +++ b/.buildkite/hooks/post-checkout @@ -4,37 +4,3 @@ CI_BUILD_START=$(date +%s) export CI_BUILD_START source ci/env.sh - -## -## Kill any running docker containers, which are potentially left over from the -## previous CI job -## -#( -# echo "+++ Killing stale docker containers" -# while read -r line; do -# read -r id image _ <<<"$line" -# -# if [[ $image =~ "solanalabs/rust" ]]; then -# if docker kill "$id" >/dev/null; then -# echo "kill $id $image" -# fi -# continue -# fi -# done < <(docker ps | tail -n +2) -#) -# -## 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 -#) diff --git a/.buildkite/scripts/build-bench.sh b/.buildkite/scripts/build-bench.sh index 8778bd5d096dcc..d1ad80389107eb 100755 --- a/.buildkite/scripts/build-bench.sh +++ b/.buildkite/scripts/build-bench.sh @@ -8,24 +8,11 @@ source "$here"/common.sh agent="${1-solana}" -. ci/rust-version.sh - build_steps() { cat <