fix: remove LXC backend leftovers when the job completes #1054
No reviewers
Labels
No labels
FreeBSD
Kind/Breaking
Kind/Bug
Kind/Chore
Kind/DependencyUpdate
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Windows
linux-powerpc64le
linux-riscv64
linux-s390x
run-end-to-end-tests
run-forgejo-tests
run-multi-platform-tests
No milestone
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
forgejo/runner!1054
Loading…
Reference in a new issue
No description provided.
Delete branch "earl-warren/runner:wip-cleanup"
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?
Resolves forgejo/runner#442
When running the test from a non-root user and without this fix, it fails as follow:
3577b08471b4eb780122WIP: fix: cleanup hostexecutor directoryto WIP: fix: remove LXC backend leftovers when the job completescascading-pr updated at actions/setup-forgejo#703
WIP: fix: remove LXC backend leftovers when the job completesto fix: remove LXC backend leftovers when the job completesLooks good to me. I pulled down main, reproduced the issue, and then pulled the branch and ran through some tests with LXC & a host executor and had no cleanup errors.
The only leftovers in
~/.cache/actwere from remoteuses(eg.uses: actions/checkout@v3), which I imagine are expected to remain around for cache re-use?@mfenniak wrote in #1054 (comment):
Yes. It would be quite problematic to re-clone them every time 😁