Job timeout risk: spec/services/merge_requests/build_service_spec.rb ran much longer than expected
Why was this issue created?
spec/services/merge_requests/build_service_spec.rb was reported to have:
- exceeded Knapsack's expected runtime by at least 50%, and
- been identified as a notable pipeline bottleneck and a job timeout risk
Suggested steps for investigation
- To reproduce in CI by running test files in the same order, you can follow the steps listed here.
- Identify if a specific test case is stalling the run time. Hint: You can search the job's log for
Starting example group spec/services/merge_requests/build_service_spec.rband view the elapsed time after each test case in the proceeding lines starting with[RSpecRunTime]. - If the test file is large, consider refactoring it into multiple files to allow better test parallelization across runners.
- If the run time cannot be fixed in time, consider quarantine the spec(s) to restore performance.
Run time details
- Reported from pipeline 4758473 created at
2025-10-21T12:12:01Z
| Field | Value |
|---|---|
| Job URL | rspec-unit-pg16-single-redis-20-44 |
| Job total RSpec suite run time | expected: 34 minutes 37.6 seconds, actual: 75 minutes 35.67 seconds
|
| Spec file run time | expected: 6 minutes 30.45 seconds, actual: 16 minutes 3.32 seconds
|
| Spec file weight |
21.24% of total suite run time |