mirror of
https://github.com/nektos/act.git
synced 2026-04-26 17:35:49 +03:00
[GH-ISSUE #2491] could not rename component file ... Invalid cross-device link (os error 18) #1151
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#1151
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 @rydb on GitHub (Oct 18, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2491
Bug report info
Command used with act
Describe issue
I've been able to use act to check my rust project's CI, but recently,its been crashing do to "could not rename component file".
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
I've currently:
purged act and reinstalled it
purged docker and reinstalled it.
purged my rust toolchain and re-installed it.
and the issue still persists.
@github-actions[bot] commented on GitHub (Apr 17, 2025):
Issue is stale and will be closed in 14 days unless there is new activity
@Qyriad commented on GitHub (May 21, 2025):
I'm experiencing this issue. @rydb did you ever figure out a solution or workaround?
@rydb commented on GitHub (May 21, 2025):
I wiped my previous installation of ubuntu and installed it again to fix it. Assuming you used ubuntu/something similar, did you do a distro version migration? Maybe the issue was artifacts from ubuntu 22.04. I have a second rig that runs non-migrated ubuntu 22.04 with act that's not had this issue, and my non-migrated 24.04 fresh install hasn't run into issues either.