Job timeout risk: spec/features/merge_request/user_sees_cherry_pick_modal_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/features/merge_request/user_sees_cherry_pick_modal_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/features/merge_request/user_sees_cherry_pick_modal_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 4313790 created at 2025-06-27T16:11:55Z

Field	Value
Job URL	rspec-system-pg16-7-32
Job total RSpec suite run time	expected: 26 minutes 10.26 seconds, actual: 80 minutes 5.29 seconds
Spec file run time	expected: 1 minute 1.53 seconds, actual: 17 minutes 53.56 seconds
Spec file weight	22.34% of total suite run time

• Reported from pipeline 4670868 created at 2025-09-30T14:31:28Z

Field	Value
Job URL	rspec-system-pg16-10-32
Job total RSpec suite run time	expected: 27 minutes 18.92 seconds, actual: 80 minutes 29.07 seconds
Spec file run time	expected: 59.52 seconds, actual: 13 minutes 12.87 seconds
Spec file weight	16.42% of total suite run time