-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Getting actions workflow failed at checkout stage with error #354
Comments
Did you managed to solve? I tried execute: But I got the error again. |
I have the same issue. Any ideas/ |
@huihuiy02 Yes, I managed to fix removing the submodule: And push the changes But the error still happening in the self runner then I needed to remove the workflow folder from |
Thanks, that works for me. |
This seems to be related to the error for us. We are using self-hosted runners. UPDATE: this seems to be related to the fact that we are using this workaround to use a private actions repository for our org. The checkout happening in See also: #385 |
Would this be a suitable patch for
Tests are failing with this change. I'm currently looking into what this means. |
This should help with actions#354. The problem is that I have no idea whether such auth submodules configuration is required even when settings.submodules is false.
This action runs "git submodule foreach" early which will fail if a submodule has been deleted but is still present in the repo (see actions/checkout#354).
This action runs "git submodule foreach" early which will fail if a submodule has been deleted but is still present in the repo (see actions/checkout#354).
This action runs "git submodule foreach" early which will fail if a submodule has been deleted but is still present in the repo (see actions/checkout#354).
This action runs "git submodule foreach" early which will fail if a submodule has been deleted but is still present in the repo (see actions/checkout#354).
This action runs "git submodule foreach" early which will fail if a submodule has been deleted but is still present in the repo (see actions/checkout#354).
This action runs "git submodule foreach" early which will fail if a submodule has been deleted but is still present in the repo (see actions/checkout#354).
If at some point a PR accidentally deletes a git submodule without deleting it from .gitmodules, subsequent PRs using the same runner will fail because the checkout action will try to run `git submodule foreach ...` before updating the git repo to match the current PR and fail, we can avoid the problem by always resetting to origin/master which hopefully is always in a good state. Ideally the checkout action would be more robust: actions/checkout#354
If at some point a PR accidentally deletes a git submodule without deleting it from .gitmodules, subsequent PRs using the same runner will fail because the checkout action will try to run `git submodule foreach ...` before updating the git repo to match the current PR and fail, we can avoid the problem by always resetting to origin/master which hopefully is always in a good state. Ideally the checkout action would be more robust: actions/checkout#354
If at some point a PR accidentally deletes a git submodule without deleting it from .gitmodules, subsequent PRs using the same runner will fail because the checkout action will try to run `git submodule foreach ...` before updating the git repo to match the current PR and fail, we can avoid the problem by always resetting to origin/master which hopefully is always in a good state. Ideally the checkout action would be more robust: actions/checkout#354
If at some point a PR accidentally deletes a git submodule without deleting it from .gitmodules, subsequent PRs using the same runner will fail because the checkout action will try to run `git submodule foreach ...` before updating the git repo to match the current PR and fail, we can avoid the problem by always resetting to origin/master which hopefully is always in a good state. Ideally the checkout action would be more robust: actions/checkout#354
If at some point a PR accidentally deletes a git submodule without deleting it from .gitmodules, subsequent PRs using the same runner will fail because the checkout action will try to run `git submodule foreach ...` before updating the git repo to match the current PR and fail, we can avoid the problem by always resetting to origin/master which hopefully is always in a good state. Ideally the checkout action would be more robust: actions/checkout#354
If at some point a PR accidentally deletes a git submodule without deleting it from .gitmodules, subsequent PRs using the same runner will fail because the checkout action will try to run `git submodule foreach ...` before updating the git repo to match the current PR and fail, we can avoid the problem by always resetting to origin/master which hopefully is always in a good state. Ideally the checkout action would be more robust: actions/checkout#354
If at some point a PR accidentally deletes a git submodule without deleting it from .gitmodules, subsequent PRs using the same runner will fail because the checkout action will try to run `git submodule foreach ...` before updating the git repo to match the current PR and fail, we can avoid the problem by always resetting to origin/master which hopefully is always in a good state. Ideally the checkout action would be more robust: actions/checkout#354
If at some point a PR accidentally deletes a git submodule without deleting it from .gitmodules, subsequent PRs using the same runner will fail because the checkout action will try to run `git submodule foreach ...` before updating the git repo to match the current PR and fail, we can avoid the problem by always resetting to origin/master which hopefully is always in a good state. The `-c "http.https://github.com/.extraheader="` resets a setting set by the checkout action which causes authentication issues when fetching. Ideally the checkout action would be more robust: actions/checkout#354
#354 (comment) |
Sorry, I did abandon this solution and proposed patch since I discovered it's possible to side-step the whole issue by adding the private actions repository checkout directory to your |
I had the same problem today after adding a broken git submodule by mistake on a PR. My temporary solution was to apply a fresh start on my docker's self-runners. Would be great having a fix for this one. |
It happened to me and had taken my hours away. As far as I dug, it happened because of one "dirty" submodule on the other branch. However, its side effect was huge. The problem branch broke the whole branches' workflow. It was a nightmare. All I could do was just reboot self-hosted runners. Hope it would be fixed anytime soon. |
Rebooting the runner did help. Thank @ckcks12 |
Deleting |
Same issue. Fixed with a restart of our self-hosted runners |
Any updates? |
any update on this? |
We've experienced this as well. And I just spent some time trying to wrap my head around the problem. Best I can tell, the flow, when it breaks, goes like this:
The
I believe the intended effect is in pseudo code:
However, what is actually happening is
I expect the fix would be something like updating the code here to wrap |
I'm also now hitting this issue. My github action checks out the main repo, and then checks out another repo nested (following the exact yaml in the checkout action documentation for this scenario). After the workflow completes the last step attempts to do the post checkout job cleanup for the main repo and fails:
|
This still seems to be a problem. Now I ran into this issue as well, even though the submodule that the error talks about was deleted many months ago.
If I remember correctly i removed the submodule with
as this Stack Overflow post describes. UPDATE: Restart of runners seemed to solve the problem. |
This should help with actions#354. The problem is that I have no idea whether such auth submodules configuration is required even when settings.submodules is false.
Can we stream line this into the v2 tag? I'm hitting this with a lot of our workloads recently and the problem only seems to be getting worse |
v2 and v3 tags are updated to point to a release containing #964. Please re-open if this did not address the problem. |
This should help with actions#354. The problem is that I have no idea whether such auth submodules configuration is required even when settings.submodules is false.
Still an issue, not fixed by restarting for me. This shouldn't even be happening with # Default: false
submodules: '' correct? |
This should help with actions#354. The problem is that I have no idea whether such auth submodules configuration is required even when settings.submodules is false.
Still a problem with self-hosted runners. I created a new issue: #1358 @cory-miller You might want to re-open this and close the other issue. |
Still having this issue on self-hosted runners. [update]
So we fixed that by:
Weird thing is that, if the submodule entry does not exist in the |
On self-hosted runner the workdir may contain the files from a checkout step from a run that was scheduled on the same runner pod previously. Some of the issues mentioned in this thread are caused by that. |
Running this in PowerShell as Administrator will fix it:
|
This should help with actions#354. The problem is that I have no idea whether such auth submodules configuration is required even when settings.submodules is false.
This should help with actions#354. The problem is that I have no idea whether such auth submodules configuration is required even when settings.submodules is false.
This should help with actions#354. The problem is that I have no idea whether such auth submodules configuration is required even when settings.submodules is false.
: fatal: No url found for submodule path 'xyz' in .gitmodules Error: The process '/usr/bin/git' failed with exit code 128
The text was updated successfully, but these errors were encountered: