Job timeout risk: spec/features/commits/user_view_commits_spec.rb ran much longer than expected
Why was this issue created?
spec/features/commits/user_view_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/commits/user_view_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 4608609 created at
2025-09-15T11:07:33Z
| Field | Value |
|---|---|
| Job URL | rspec-system-pg16-11-32 |
| Job total RSpec suite run time | expected: 27 minutes 38.28 seconds, actual: 81 minutes 12.22 seconds
|
| Spec file run time | expected: 36.76 seconds, actual: 43 minutes 11.59 seconds
|
| Spec file weight |
53.19% of total suite run time |
- Reported from pipeline 4935277 created at
2025-12-03T23:36:46Z
| Field | Value |
|---|---|
| Job URL | rspec-system-pg16-16-32 |
| Job total RSpec suite run time | expected: 33 minutes 51.89 seconds, actual: 80 minutes 47.22 seconds
|
| Spec file run time | expected: 1 minute 4.61 seconds, actual: 60 minutes 18.41 seconds
|
| Spec file weight |
74.65% of total suite run time |
Edited by KNAPSACK_REPORT_ISSUES_PROJECT_TOKEN