Job timeout risk: spec/requests/api/discussions_spec.rb ran much longer than expected
Why was this issue created?
spec/requests/api/discussions_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/requests/api/discussions_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 4794795 created at
2025-10-29T18:31:49Z
| Field | Value |
|---|---|
| Job URL | rspec-integration-pg16-20-20 |
| Job total RSpec suite run time | expected: 34 minutes 20.14 seconds, actual: 71 minutes 4.64 seconds
|
| Spec file run time | expected: 6 minutes 10.8 seconds, actual: 11 minutes 51.11 seconds
|
| Spec file weight |
16.67% of total suite run time |