Job timeout risk: spec/features/projects/commits/user_views_commits_spec.rb ran much longer than expected
Why was this issue created?
spec/features/projects/commits/user_views_commits_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/features/projects/commits/user_views_commits_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 5244542 created at
2026-02-23T08:14:01Z
| Field | Value |
|---|---|
| Job URL | rspec-system-pg17-20-32 |
| Job total RSpec suite run time | expected: 28 minutes 2.56 seconds, actual: 81 minutes 27.0 seconds
|
| Spec file run time | expected: 51.5 seconds, actual: 60 minutes 34.82 seconds
|
| Spec file weight |
74.38% of total suite run time |