-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
GitHub Actions fails with "fatal: ls-files -i must be used with either -o or -c" #23
Comments
The Ubuntu-20.04 runner does not yet work with the actions we are using. URL: voxpupuli/gha-puppet#23 Signed-off-by: Samuli Seppänen <samuli@openvpn.net>
Making "runs-on" configurable would probably allow working around this and other image-related issues. Right now "runs-on" is hardcoded to "ubuntu-latest": |
Just for reference: "ubuntu-latest" changed from 20.04 to 22.04 some time after August 2022: |
The error is probably coming from: puppetlabs/puppetlabs_spec_helper#346 If you want, you can test the master branch of puppetlabs_spec_helper and see if the error disappears. |
As @bastelfreak said: this is something in puppetlabs_spec_helper and I'm really hoping they'll do a release. Nothing more we can do. |
URL: voxpupuli/gha-puppet#23 Signed-off-by: Samuli Seppänen <samuli@openvpn.net>
URL: voxpupuli/gha-puppet#23 Signed-off-by: Samuli Seppänen <samuli@openvpn.net>
URL: voxpupuli/gha-puppet#23 Signed-off-by: Samuli Seppänen <samuli@openvpn.net>
URL: voxpupuli/gha-puppet#23 Signed-off-by: Samuli Seppänen <samuli@openvpn.net>
Thanks for the info @bastelfreak and @ekohl! I was unable to test my "revert back to Ubuntu 20.04 runner" workaround (see above) because referring to public non-GitHub Marketplace GitHub Action workflows seems to broken now. |
We did create f744ec2. Perhaps we should create a new tag again, which is something we don't do that much. |
Hi,
It seems that voxpupuli/gha-puppet/.github/workflows/basic.yml@v1 fails now with an error related to Git syntax errors:
This has been reported by other projects and seems related to a Git version that breaks backwards compatibility. This issue seems to affect Ubuntu 20.04 and 22.04 images. Here's another report of what seems to be the same issue:
The relevant raw logs from GitHub Action here:
The text was updated successfully, but these errors were encountered: