mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #1307] actions/checkout lstat of non-existent file causes failure #707
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#707
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @GMNGeoffrey on GitHub (Aug 16, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/1307
Bug report info
Command used with act
Describe issue
When running this workflow act fails trying lstat a directory or file that doesn't exist. I don't know why it's referencing this directory that doesn't exist and has never existed at the root of the repo.
My actual workflow is at
github.com/iree-org/iree@e91e0896c5. I've attached the pared down version of the workflow file, which also reproduced the issue. I also deleted all the other workflow files in the directory, since it seemed to be parsing those.Link to GitHub repository
https://github.com/iree-org/iree
Workflow content
Relevant log output
Short log:
Full log:
Full log
Additional information
No response
@ChristopherHX commented on GitHub (Aug 16, 2022):
This was a bug of act v0.2.29, but in v0.2.30 a fix has been merged https://github.com/nektos/act/pull/1282.
What about upgrading act to v0.2.30? There is a bug in submodule handling in v0.2.29.
@GMNGeoffrey commented on GitHub (Aug 16, 2022):
Sure I'm happy to upgrade :-) I searched the issues and didn't find anything open or closed that looked like the same issue
@GMNGeoffrey commented on GitHub (Aug 16, 2022):
Huh, I don't quite understand why I was affected by that issue or why it only just started happening. The submodule name does match the git repo name. But no matter, upgrading to 0.2.30 fixed the issue, thanks!