node-compile-windows is failing since 2026-07-25 on `win-vs2022_clang(-arm64)` with error `remote rejected`

[trivikr]

https://ci.nodejs.org/job/node-compile-windows/nodes=win-vs2022_clang/

Last successful build

> git push "binary_tmp@67.158.54.159:binary_tmp.git" "+jenkins-node-test-commit-windows-fanned-9ab72dfd8687d5483954ea98d4313175e52505b0-bin-win-vs2022_clang" 
Warning: Permanently added '67.158.54.159' (ED25519) to the list of known hosts.
To 67.158.54.159:binary_tmp.git
 * [new branch]              jenkins-node-test-commit-windows-fanned-9ab72dfd8687d5483954ea98d4313175e52505b0-bin-win-vs2022_clang -> jenkins-node-test-commit-windows-fanned-9ab72dfd8687d5483954ea98d4313175e52505b0-bin-win-vs2022_clang

https://ci.nodejs.org/job/node-compile-windows/nodes=win-vs2022_clang/67750/console

First failed build

> git push "binary_tmp@67.158.54.159:binary_tmp.git" "+jenkins-node-test-commit-windows-fanned-afee66ee6355751048d050bf757fa721a4c2ba31-bin-win-vs2022_clang" 
Warning: Permanently added '67.158.54.159' (ED25519) to the list of known hosts.
remote: fatal: unresolved deltas left after unpacking        
error: remote unpack failed: unpack-objects abnormal exit
To 67.158.54.159:binary_tmp.git
 ! [remote rejected]         jenkins-node-test-commit-windows-fanned-afee66ee6355751048d050bf757fa721a4c2ba31-bin-win-vs2022_clang -> jenkins-node-test-commit-windows-fanned-afee66ee6355751048d050bf757fa721a4c2ba31-bin-win-vs2022_clang (unpacker error)
error: failed to push some refs to '67.158.54.159:binary_tmp.git'

https://ci.nodejs.org/job/node-compile-windows/nodes=win-vs2022_clang/67751/console

[trivikr]

Same failures in https://ci.nodejs.org/job/node-compile-windows/nodes=win-vs2022_clang-arm64/

[trivikr]

This was fixed as part of work on security releases

The CI run at Jul 27, 2026, 11:43:51 AM was successful
https://ci.nodejs.org/job/node-compile-windows/nodes=win-vs2022_clang/67759/

[trivikr]

Keeping it open for @nodejs/build team to comment on what the issue was, for future reference.

[sxa]

This is effectively a duplicate of #4408 - I didn't fix this problem separately but it was the same underlying symptom with one of the repositories on the workspace machines being invalid.