fix: ensure log buffer flush even if a command error occurs in host & lxc executor #1375
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
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo/runner!1375
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "mfenniak/forgejo-runner:flush-logs-on-hostexecutor-error"
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?
Probably fixes #1374. As soon as subcommand in the host & LXC executor was failing with an error, it would cause a skip of the code path that ensured the log buffer flush was complete.
fix: don't skip flushing output buffers when command error occursto fix: ensure log buffer flush even if a command error occurrscascading-pr updated at actions/setup-forgejo#886
fix: ensure log buffer flush even if a command error occurrsto fix: ensure log buffer flush even if a command error occurs in host & lxc executor