Job timeout risk: spec/mailers/notify_spec.rb ran much longer than expected
Why was this issue created?
spec/mailers/notify_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/mailers/notify_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 3258189 created at
2024-09-30T01:15:58Z
| Field | Value |
|---|---|
| Job URL | rspec-integration-pg14-single-redis-9-20 |
| Job total RSpec suite run time | expected: 36 minutes 18.21 seconds, actual: 80 minutes 2.07 seconds
|
| Spec file run time | expected: 13 minutes 10.82 seconds, actual: 25 minutes 25.22 seconds
|
| Spec file weight |
31.76% of total suite run time |
- Reported from pipeline 4852311 created at
2025-11-12T23:46:18Z
| Field | Value |
|---|---|
| Job URL | rspec-integration-pg16-8-20 |
| Job total RSpec suite run time | expected: 34 minutes 7.09 seconds, actual: 79 minutes 42.65 seconds
|
| Spec file run time | expected: 11 minutes 31.16 seconds, actual: 30 minutes 57.97 seconds
|
| Spec file weight |
38.85% of total suite run time |
Edited by KNAPSACK_REPORT_ISSUES_PROJECT_TOKEN