[RSpec random order] Processed 1 specs: all failed ❌

RSpec Order Dependency Check Results

Processed 1 spec files from spec/support/rspec_order_todo.yml:

• 0 specs passed and can now run in random order ✅
• 1 specs failed and were moved to spec/support/rspec_order_failures.yml ❌ None in this batch

❌ Failed specs with bisect analysis (1):

• ee/spec/controllers/admin/projects_controller_spec.rb
  • Bisect: ✅ rspec './ee/spec/controllers/admin/projects_controller_spec.rb[1:1:1:1:2:1]' --seed 20250924 --format documentation

📊 Progress Summary:

• Processed this batch: 1 specs
• Passed (can run randomly): 0 specs
• Failed (moved to failure list): 1 specs
• Remaining in TODO: 7971 specs
• TODO list cleanup: Removed 1 processed entries

🐛 Debugging Failed Specs:

For specs that failed the order dependency check, use the provided bisect commands to:

1. Reproduce the issue: Run the minimal reproduction command
2. Identify dependencies: See which other specs are needed to make it pass
3. Fix the root cause: Remove shared state or add proper cleanup
4. Re-test: Run the spec again to verify the fix

---

Related to: #407877 (closed)

The order dependency checks were performed using scripts/rspec_check_order_dependence. Bisect analysis was run on failed specs to provide debugging information.

This change was generated by gitlab-housekeeper locally using the Keeps::RspecOrderChecker keep.

To provide feedback on your experience with gitlab-housekeeper please create an issue with the label GitLab Housekeeper and consider pinging the author of this keep.