Job timeout risk: spec/requests/api/commits_spec.rb ran much longer than expected

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Why was this issue created?

spec/requests/api/commits_spec.rb was reported to have:

1. exceeded Knapsack's expected runtime by at least 50%, and
2. been identified as a notable pipeline bottleneck and a job timeout risk

Suggested steps for investigation

1. To reproduce in CI by running test files in the same order, you can follow the steps listed here.
2. 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/commits_spec.rb and view the elapsed time after each test case in the proceeding lines starting with [RSpecRunTime].
3. If the test file is large, consider refactoring it into multiple files to allow better test parallelization across runners.
4. If the run time cannot be fixed in time, consider quarantine the spec(s) to restore performance.

Run time details

• Reported from pipeline 4019690 created at 2025-04-08T22:21:25Z

Field	Value
Job URL	rspec-integration-pg16-19-20
Job total RSpec suite run time	expected: 25 minutes 25.14 seconds, actual: 71 minutes 40.78 seconds
Spec file run time	expected: 4 minutes 58.03 seconds, actual: 14 minutes 45.23 seconds
Spec file weight	20.58% of total suite run time

• Reported from pipeline 4841517 created at 2025-11-10T19:16:09Z

Field	Value
Job URL	rspec-integration-pg16-single-db-ci-connection-15-20
Job total RSpec suite run time	expected: 32 minutes 38.55 seconds, actual: 70 minutes 54.95 seconds
Spec file run time	expected: 6 minutes 28.31 seconds, actual: 15 minutes 3.03 seconds
Spec file weight	21.22% of total suite run time