-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'spawn gpg ENOENT' error when building with DMD (self-hosted runner, win 10 x64) #56
Comments
Perhaps the problem is in the generated paths for gpg tool... |
I looked at the action source codes and saw that there is a path conversion for msys. Nowhere did I see this in the requirements for action. I am using gpg4win. |
hm this action is using gpg assuming it is just installed. Looks like in the preinstalled software list GPG is not included, so it's probably being used from msys here. Don't think there is any better solution than installing it from msys for self hosted runners. |
The fact is that I run runner as a service, so I will need to "do squats and push-ups" so that commands from under it are executed in msys. I have ideas how to do this without fixing the action. Perhaps I can fix this in the workflow. In the worst case, you just have to run runner from under msys. |
An
spawn gpg ENOENT
error occurred while trying to build a project on a self-hosted runner with DMD (dmd-latest).What could be the problem?
OS: Windows 10 x64, 21H2 19044.1706
CPU: AMD Ryzen 7 3700X
RAM: 32GB DDR4
Error:
Project: https://github.com/ttldtor/diff
Logs: logs_9.zip
The path to gpg is in PATH. I can run it from terminal.
All other builds (and ldc on self-hosted logs_ldc.zip) were successful.
The user responsible for runner has enough rights to write to or read from the directory.
This is how a "successful" part of build under Windows (github runner) using DMD looks like:
Please, help.
The text was updated successfully, but these errors were encountered: