Tweak gitlab CI concurrency, parallelism and test running order for 11 minute test runs

related issue is RTBC, so marking this so maybe they can merged together.

Merge conflict:

diff --cc core/scripts/run-tests.sh
index 00d32f56a1,cc5b830f41..0000000000
--- a/core/scripts/run-tests.sh
+++ b/core/scripts/run-tests.sh
@@@ -1037,7 -1037,7 +1037,11 @@@ function simpletest_script_get_test_lis
    if ((int) $args['ci-parallel-node-total'] > 1) {
      $slow_tests_per_job = ceil(count($slow_tests) / $args['ci-parallel-node-total']);
      $tests_per_job = ceil(count($test_list) / $args['ci-parallel-node-total']);
++<<<<<<< HEAD
 +    $test_list = array_slice($slow_tests, ($args['ci-parallel-node-index'] -1) * $slow_tests_per_job, $slow_tests_per_job) + array_slice($test_list, ($args['ci-parallel-node-index'] - 1) * $tests_per_job, $tests_per_job);
++=======
+     $test_list = array_merge(array_slice($slow_tests, ($args['ci-parallel-node-index'] -1) * $slow_tests_per_job, $slow_tests_per_job), array_slice($test_list, ($args['ci-parallel-node-index'] - 1) * $tests_per_job, $tests_per_job));
++>>>>>>> 11.x
    }

Going to expand the scope here but also postpone it on the top 3-4 targets from 📌 [meta] Refactor ultra-slow tests Active

Actually postponing.

Committed most issues soft-blocking this:

• 📌 Use 'needs' instead of 'dependencies' to speed up gitlab CI jobs and run phpstan first RTBC
• 📌 Mark some more tests #slow Needs review
• 📌 Consolidate methods in jsonapi FileUploadTest Fixed
• 📌 Split up LayoutBuilderTest Fixed

This could be reviewed while the other issue is open since there's no hard dependency, it would just be good to compare a pipeline here once all the other issues are in to the 11.x branch tests to have a real comparison.

Missed a child issue, although it's RTBC. Did a rebase last might but gitlab was erroring out due to the docker outage, so going to try luck on the pipeline this morning.

Here's the last run: https://git.drupalcode.org/project/drupal/-/pipelines/24975

14m28s but if you click through to the individual jobs for functional and functional javascript tests you can see the ckeditor5, configtranslationui, and updatesemver tests on three out of three of the longest runs. 📌 Split up ConfigTranslationUiTest RTBC wasn't on the list here so back to PP-3.

About to push a commit to slightly reorder the yarn lint jobs, we might be able to squeeze 10-30 seconds from that (start eslint jobs while the other lint jobs are queuing).

https://git.drupalcode.org/project/drupal/-/pipelines/25005 13 minutes 2 seconds.

Obviously there's a lot of variation between jobs but looking more like it should. I am pretty confident the remaining three test refactors will take two more minutes off. The best time I've seen on the omnibus MR was 11 minutes 1 second.

Committed following, back to PP-1:

• 📌 CKEditor 5's Functional JS tests take a long time to run Fixed
• 📌 Split up ConfigTranslationUiTest RTBC

Changes look good to me. Mostly adding parallel to some jobs and changing order.

RTBC.

Rebased with all-but-one of the blockers committed now.

12 minutes 25 seconds

https://git.drupalcode.org/project/drupal/-/pipelines/25143

Not a blocker but potentially another 30 seconds from 📌 Move config ui date format test to the dedicated test class Needs review .

📌 Split up update semver tests Fixed is in! Rebased this to get a fresh run.

12m35s but there was a lot of 'waiting for pod' on the lint steps which always leads to variation. https://git.drupalcode.org/project/drupal/-/pipelines/25936

Longest functional test run duration was 6m6s, the two issues linked in #3388952-27: Tweak gitlab CI concurrency, parallelism and test running order for 11 minute test runs → will bring that down further but a small incremental changes on top of this.

Kicked off one more pipeline: https://git.drupalcode.org/project/drupal/-/pipelines/25943 10m31s - fastest one so far, mostly the difference between pod waiting times I think compared to the previous run.

lauriii → closed merge request !4844

I remember when I started contributing to Drupal core, the test runs were around this long. It's unbelievable that we have been able to match that
with the amount of test coverage we have added since then 🤯

Committed bd32c83 and pushed to 11.x. Thanks!

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