celerity / celerity/slurmactiond
Time-out jobs when GitHub fails to send a status update
- Dominant language
- Rust
- Stars
- 13
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
I have observed a situation where a runner completes a job, but slurmactiond is not notified of the job's completion and it sticks around in the overview indefinitely. This can be remedied by a) timing out jobs after x minutex when their runner has finished or b) by timing out any job after, say, 24 hours.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how slurmactiond receives GitHub job status updates and retains completed jobs in the overview. Confirm the failure case where a runner finishes without a completion notification; done when jobs are reliably removed or timed out according to an agreed timeout policy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- backend, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100