Job timeout risk: spec/features/merge_request/user_uses_quick_actions_spec.rb ran much longer than expected
Why was this issue created?
spec/features/merge_request/user_uses_quick_actions_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/merge_request/user_uses_quick_actions_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 4129757 created at
2025-05-07T21:58:38Z
| Field | Value |
|---|---|
| Job URL | rspec-system-pg16-11-32 |
| Job total RSpec suite run time | expected: 25 minutes 6.17 seconds, actual: 78 minutes 41.5 seconds
|
| Spec file run time | expected: 8 minutes 11.43 seconds, actual: 26 minutes 22.74 seconds
|
| Spec file weight |
33.52% of total suite run time |
- Reported from pipeline 5159061 created at
2026-02-02T23:40:57Z
| Field | Value |
|---|---|
| Job URL | rspec-system-pg16-22-32 |
| Job total RSpec suite run time | expected: 30 minutes 48.59 seconds, actual: 75 minutes 33.94 seconds
|
| Spec file run time | expected: 6 minutes 42.98 seconds, actual: 20 minutes 2.37 seconds
|
| Spec file weight |
26.52% of total suite run time |
Edited by KNAPSACK_REPORT_ISSUES_PROJECT_TOKEN