Switching scope to running
What does this MR do and why?
This change fixes a bug in the system that tracks which build jobs have timed out. Previously, the code was incorrectly identifying failed or completed builds as "timed out", as there are lingering "zombie" records in Ci::RunningBuild.
The fix adds a filter (.running) to ensure only actively running builds are considered for timeout detection. A test was also added to verify that non-running builds (like failed ones) are properly excluded from the timeout check.
This prevents the system from mistakenly flagging already-finished builds as timed out, making the timeout detection more accurate.
References
Scope being updated with running :
- Cold cache: https://console.postgres.ai/gitlab/gitlab-production-ci/sessions/48319/commands/145734
- Warm cache: https://console.postgres.ai/gitlab/gitlab-production-ci/sessions/48463/commands/145703
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.