[meta] Determine impact of [#3350972] fix in off-canvas.js on currently disabled FunctionalJavascript tests

Actually, 1500 runs is not statistically sufficient to prove something is fixed. Each test should be queued against a MySQL or Maria database 5000-8000 times. This can be accomplished by queuing a patch that runs the test 1000x for the required number of times. Don't use Postgres or SQLite databases for this.

Ok, I was under the impression we use 1500x as the magic number, I'll just requeue the 1500x patches 4 more times.

However, that leaves us with patches that are too slow for a 1500x run in the Drupal CI environment and hit the timeout like 📌 [no random test failure] Try to un-skip and fix LayoutBuilderDisableInteractionsTest::assertContextualLinksClickable in context of [#3353085] Fixed where I had to down-scale to a 500x run.

Do we need to requeue those patches (at least) 9 more times?

However, that leaves us with patches that are too slow for a 1500x run in the Drupal CI environment and hit the timeout like [#3353103]where I had to down-scale to a 500x run. Do we need to requeue those patches (at least) 9 more times?

If so, can I tag those issues as "Novice" and the person that requeues it for the required number of reruns will receive credit for that?

Yep I have queued 10 or 15 jobs in the past for tests that are too slow to run more per job.

I can just queue the jobs now; not sure why that would be a novice task.

Fixing attribution.

We might have resolved 🐛 [random test failure] LayoutBuilderQuickEditTest::testQuickEditIgnoresDuplicateFields() Active too (9.5 only).

Sadly not: https://www.drupal.org/project/drupal/issues/3210432#comment-15007163 🐛 [random test failure] LayoutBuilderQuickEditTest::testQuickEditIgnoresDuplicateFields() Active

Closing as all of its children are in an end-status.

@Spokje, thank you for managing this and working on the child issues !

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