Job timeout risk: spec/features/merge_request/creating_mr_for_projects_with_different_visibility_spec.rb ran much longer than expected

Why was this issue created?

spec/features/merge_request/creating_mr_for_projects_with_different_visibility_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/creating_mr_for_projects_with_different_visibility_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 4886323 created at 2025-11-21T00:08:18Z

Field	Value
Job URL	rspec-system-pg16-single-db-ci-connection-4-32
Job total RSpec suite run time	expected: 29 minutes 53.88 seconds, actual: 81 minutes 16.6 seconds
Spec file run time	expected: 37.71 seconds, actual: 24 minutes 20.68 seconds
Spec file weight	29.95% of total suite run time