ssbarnea
commented
2 days ago I tried to use explorer to unarchive the zip and while it did unarchive most files, it failed with "Destination Path Too Long".
What is worse here is that I installed the runner in the root of the main partition, the default location recommended by the docs. The are barely any options to reduce the path length.
I applied the long path enablement documented on https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=powershell and restarted the system in order to ensure that all processed benefit from it. Tested again with explorer and it was still unable to archive the zip file.
Still, unarchiving the zip to C:\1\ folder succeeded. Still, that is not an option as we have no control on how github runners are using temp folders.
The fact that other Windows runners can clone this repository makes me wonder why it can work on some Windows machine an not others.
It seems that the checkout action fails to checkout with a cryptic error on self-hosted runners. Error looks like below:
This is a fresh Windows 10 PRO x64 installation with the runner configured to run as a service.
Execution https://github.com/ansible/vscode-ansible/actions/runs/11933502609/job/33260689830?pr=1664
Current runner version: '2.320.0'
One interesting message that I seen before the failure was
To create a local Git repository instead, add Git 2.18 or higher to the PATH-- which is unexpected because it was still there even after I manually installed git and checked that git was in PATH.I was able to reproduce the error when running in local console and I observed that
C:\actions-runner\_work\vscode-ansible\vscode-ansible\4eb22f6a-3455-4306-b3b2-63ee299a73c8folder exists but it is empty.