Job timeout risk: spec/features/boards/issue_ordering_spec.rb ran much longer than expected
Why was this issue created?
spec/features/boards/issue_ordering_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/boards/issue_ordering_spec.rb
and 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 2814220 created at
2024-05-24T11:34:05Z
Field | Value |
---|---|
Job URL | rspec-system-pg14-single-db-23-32 |
Job total RSpec suite run time | expected: 20 minutes 9.91 seconds , actual: 70 minutes 6.33 seconds
|
Spec file run time | expected: 1 minute 13.72 seconds , actual: 10 minutes 43.15 seconds
|
Spec file weight |
15.29% of total suite run time |