bug: timeout-minutes on a job step is not respected #979
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo/runner#979
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?
Can you reproduce the bug on the Forgejo test instance?
No
Description
See this run: https://codeberg.org/ziglang/zig/actions/runs/9
In this commit, the
timeout-minutesvalue is5for all steps, yet none of them get canceled.We're currently evaluating Forgejo Actions on Codeberg for the development of Zig and this is a serious concern for us since we fairly often deal with nondeterministic hangs, and we need to know that jobs will be reliably timed out when such hangs occur.
Forgejo Version
Codeberg current (v12.x?)
Runner Version
v11.0.0
How are you running Forgejo?
Codeberg
How are you running the Runner?
Built from source with
make buildbut otherwise following the installation guide.Logs
I can attach the full debug log if desired (once the job completes), but there is nothing that looks at all relevant, except:
So, it's parsing the correct value; it just doesn't seem to take effect in any meaningful way - there isn't even an attempt to cancel the job.
Workflow file
ziglang/zig@aa36c89588/.forgejo/workflows/ci.yamlNote: The run linked above did get canceled, but that was because I made an unrelated push to the same branch, not due to a timeout.
I confirm the timeout-minutes for jobs is currently a noop.
The timeout-minutes is implemented and documented for steps and that could be a workaround until this is fixed
https://forgejo.org/docs/next/user/actions/reference/#jobsjob_idstepstimeout-minutes
I have verified it works as expected at https://v13.next.forgejo.org/earl-warren/testtimeout-minutes/actions/runs/2/jobs/0/attempt/1
The documentation part of the fix is at https://codeberg.org/forgejo/docs/pulls/1459
I can confirm that a step-level
timeout-minutesworks for us as well. Thanks for the workaround, and the fix PR!