Spike: Refine Job timeouts still not working

Note to everyone noticing related behaviour.

I am starting to research the problem and trying to identify the flow, potential failure points and their intersection. On that endeavour as already stated the hard part is figuring out where to strategically place more monitoring points.

  1. Please follow the same template as in #457222 (comment 2665264202) and provide as much info as possible.
  2. Tag panoskanell to the comment so that I don't miss it.
  3. Logs should be < 1 month old for GitLab.com occurrences

Summary - Why is this spike needed?

It was noted in the issue discussion that this issue was previously discovered to be in the Rails code, but that discussion nor the details of the discovery were not documented. As such we need to re-identify the cause and add the proposal to the issue.

Timebox Expectations

2 weeks

Expected Outcomes

  • Possible cause(s) are determined
  • Technical proposal added to #
  • Weight added to gitlab-runner#27040 (closed)

Links/References

  • #334353 (comment 1202488542)
  • gitlab-runner#29086 (comment 1202449854)
  • gitlab-runner#4147 (comment 224456292)
Edited Sep 03, 2025 by Panos Kanellidis
Assignee Loading
Time tracking Loading