Enable running the same test multiple times on gitlab ci for random test failures

Sounds like a race condition that can be fixed using a targeted "wait".

Doesn't seem to fail (frequently) on Drupal CI, no idea and/or documentation how to run a 500x-MR on GitLab, so not much in it for me here.

Re-titling for the changed scope.

I have one small question on the help text, but could go either way on that.

This is considerably more ergonomic than 'find a patch that runs the same test 1,000 times from another issue, edit the classname to the one you want, then upload it to Drupal CI', or 'remember how to modify drupalci.yml so it will run the same test 1,000 times', and given we can't add custom help text to the actual gitlab UI is pretty self-documenting with the error message.

The parallel runs are less useful when you have to manually add the variables, but it will allow 'proof of non-failure' to be done more efficiently - i.e. when we want to run the test thousands of times instead of a couple hundred. And we can tweak this as we go along to support more things.

Successfully used this for 🐛 [random test failure] ComponentsTaggedReleaseTest sometimes fails Needs review .

Made one commit here - to remove parallel because the gitlab UI was showing the entire pipeline as still in progress, and I think this might be due to parallel manual jobs.

One more idea here, although it could happen in a follow-up, would be to add an extra variable for REPEAT, then in the pipeline default that to 100 but use it to override the number of runs, so someone can put 1000 for a unit test if they want/need to.

Going to go ahead and commit this to unblock more random rest failure sleuthing. Committed/pushed to 11.x and cherry-picked to 10.2.x, thanks!

Automatically closed - issue fixed for 2 weeks with no activity.