Release scripts fail for Bazel 3.7.2rc1 on arm

[katre]

The ARM build for 3.7.2rc1 failed due to not finding the release branch. See https://buildkite.com/bazel-trusted/bazel-release/builds/197#1f193861-cb84-4146-b320-64ff12016780 for details:

docker run -it --rm --init --volume /var/lib/buildkite-agent/builds/arm1-bazel-build/bazel-trusted/bazel-release:/workdir --volume /etc/group:/etc/group:ro --volume /etc/passwd:/etc/passwd:ro --volume /opt:/opt:ro --volume /var/lib/buildkite-agent:/var/lib/buildkite-agent --volume /var/lib/gitmirrors:/var/lib/gitmirrors:ro --workdir /workdir -u 999:998 --env BUILDKITE_JOB_ID --env BUILDKITE_BUILD_ID --env BUILDKITE_AGENT_ACCESS_TOKEN --volume /usr/bin/buildkite-agent:/usr/bin/buildkite-agent --env BUILDKITE_ARTIFACT_UPLOAD_DESTINATION --env GOOGLE_APPLICATION_CREDENTIALS --privileged --env BUILDKITE_AGENT_META_DATA_QUEUE --env BUILDKITE_TAG --env BUILDKITE_BUILD_ID --env BUILDKITE_COMMIT --env BUILDKITE_PLUGINS --env CI --env BUILDKITE_TIMEOUT --env BUILDKITE_PULL_REQUEST_REPO --env BUILDKITE_PIPELINE_SLUG --env BUILDKITE_BUILD_CREATOR_TEAMS --env BUILDKITE_RETRY_COUNT --env BUILDKITE_PULL_REQUEST_BASE_BRANCH --env BUILDKITE_AGENT_META_DATA_KIND --env BUILDKITE_PIPELINE_PROVIDER --env BUILDKITE_AGENT_ID --env BUILDKITE_REBUILT_FROM_BUILD_NUMBER --env BUILDKITE_PIPELINE_DEFAULT_BRANCH --env BUILDKITE_PIPELINE_ID --env BUILDKITE_AGENT_NAME --env BUILDKITE_PIPELINE_NAME --env BUILDKITE_TRIGGERED_FROM_BUILD_NUMBER --env BUILDKITE_BUILD_CREATOR --env BUILDKITE_BUILD_URL --env BUILDKITE_JOB_ID --env BUILDKITE_PROJECT_PROVIDER --env BUILDKITE_LABEL --env BUILDKITE_TRIGGERED_FROM_BUILD_ID --env BUILDKITE_BUILD_CREATOR_EMAIL --env BUILDKITE_SOURCE --env BUILDKITE_STEP_KEY --env BUILDKITE_BRANCH --env BUILDKITE --env BUILDKITE_BUILD_AUTHOR_EMAIL --env BUILDKITE_REBUILT_FROM_BUILD_ID --env BUILDKITE_TRIGGERED_FROM_BUILD_PIPELINE_SLUG --env BUILDKITE_PROJECT_SLUG --env BUILDKITE_REPO --env BUILDKITE_MESSAGE --env BUILDKITE_STEP_ID --env BUILDKITE_ORGANIZATION_SLUG --env BUILDKITE_BUILD_AUTHOR --env BUILDKITE_SCRIPT_PATH --env BUILDKITE_BUILD_NUMBER --env BUILDKITE_ARTIFACT_PATHS --env BUILDKITE_AGENT_META_DATA_OS --env BUILDKITE_COMMAND --env BUILDKITE_PULL_REQUEST --network host --label com.buildkite.job-id=adde44ab-6f32-4ac9-a078-76e2384ff988 gcr.io/bazel-public/centos7-releaser /bin/bash -e -c $'git fetch origin master\ngit fetch --force origin refs/notes/*:refs/notes/*\ngit checkout release-3.7.2rc1\n\nrelease_name=$(buildkite-agent meta-data get "release_name")\necho "release_name = \\"$release_name\\""\n\nbazel build --sandbox_tmpfs_path=/tmp //src:bazel\nmkdir output\ncp bazel-bin/src/bazel output/bazel\n\noutput/bazel build \\\n    -c opt \\\n    --stamp \\\n    --sandbox_tmpfs_path=/tmp \\\n    --embed_label "${release_name}" \\\n    --workspace_status_command=scripts/ci/build_status_command.sh \\\n    src/bazel\n\nmkdir artifacts\ncp "bazel-bin/src/bazel" "artifacts/bazel-${release_name}-linux-arm64"\n\ncd artifacts\nbuildkite-agent artifact upload "*"\n'
--
  | From https://github.com/bazelbuild/bazel
  | * branch            master     -> FETCH_HEAD
  | error: pathspec 'release-3.7.2rc1' did not match any file(s) known to git.

I don't know if it has the wrong upstream, or just failed to sync first, but it's very confusing.

[katre]

Ping @philwo

[philwo]

I think this was fixed by 1a045ef.