"conda-forge-admin, please restart ci" bot command failing

[matthewfeickert]

Solution to issue cannot be found in the documentation.

• [x] I checked the documentation.

Issue

As noted in https://github.com/conda-forge/hatchling-feedstock/pull/62, in recent conda-forge feedstocks using the @conda-forge-admin, please restart ci command will fail.

Duplicating the information from https://github.com/conda-forge/hatchling-feedstock/pull/62#issuecomment-2472036329:

In the CI logs

Starting: Checkout conda-forge/hatchling-feedstock@refs/pull/62/merge to s
==============================================================================
Task         : Get sources
Description  : Get sources from a repository. Supports Git, TfsVC, and SVN repositories.
Version      : 1.0.0
Author       : Microsoft
Help         : [More Information](https://go.microsoft.com/fwlink/?LinkId=798199)
==============================================================================
Syncing repository: conda-forge/hatchling-feedstock (GitHub)
git version
git version 2.47.0
git lfs version
git-lfs/3.5.1 (GitHub; linux amd64; go 1.21.8)
git init "/home/vsts/work/1/s"
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint:   git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint:   git branch -m <name>
Initialized empty Git repository in /home/vsts/work/1/s/.git/
git remote add origin https://github.com/conda-forge/hatchling-feedstock
git config gc.auto 0
git config core.longpaths true
git config --get-all http.https://github.com/conda-forge/hatchling-feedstock.extraheader
git config --get-all http.extraheader
git config --get-regexp .*extraheader
git config --get-all http.proxy
git config http.version HTTP/1.1
git --config-env=http.extraheader=env_var_http.extraheader fetch --force --tags --prune --prune-tags --progress --no-recurse-submodules origin   +refs/heads/*:refs/remotes/origin/* +refs/pull/62/merge:refs/remotes/pull/62/merge
fatal: couldn't find remote ref refs/pull/62/merge
##[warning]Git fetch failed with exit code 128, back off 4.987 seconds before retry.
git --config-env=http.extraheader=env_var_http.extraheader fetch --force --tags --prune --prune-tags --progress --no-recurse-submodules origin   +refs/heads/*:refs/remotes/origin/* +refs/pull/62/merge:refs/remotes/pull/62/merge
fatal: couldn't find remote ref refs/pull/62/merge
##[warning]Git fetch failed with exit code 128, back off 8.168 seconds before retry.
git --config-env=http.extraheader=env_var_http.extraheader fetch --force --tags --prune --prune-tags --progress --no-recurse-submodules origin   +refs/heads/*:refs/remotes/origin/* +refs/pull/62/merge:refs/remotes/pull/62/merge
fatal: couldn't find remote ref refs/pull/62/merge
##[error]Git fetch failed with exit code: 128
Finishing: Checkout conda-forge/hatchling-feedstock@refs/pull/62/merge to s

Installed packages

This is happening in the CI job before anything is installed.

Environment info

This is happening in the CI job before anything is installed.

[matthewfeickert]

I see that @jakirkham has identified (https://github.com/conda-forge/hatchling-feedstock/pull/62#issuecomment-2472041715) this is related to https://github.com/conda-forge/conda-forge.github.io/issues/2346 👀

[beckermr]

This is azure clearly. Unless they have supplied new api endpoints to restart jobs, we should remove the command

[jakirkham]

It is worth noting that this issue doesn't happen all the time, but it does happen sometimes

Also it can happen with just closing and reopening a PR or in some cases pushing a commit

These issues sometimes clear up on their own

Here's an extreme example: https://github.com/conda-forge/cuda-nvvp-feedstock/pull/14

[jakirkham]

Instead of pulling the command (given this is not repeatably persistent nor unique to it), would recommend we raise this issue with Azure

Clearly they made a change recently, which is causing issues