Try to speed up build tests

Have a small theory that because build tests use composer operations, which can fork multiple processes, that we might just benefit from allocating more CPU. A test that takes 180 seconds on gitlab takes just over a minute on my local (without everything being on a ramdisk).

If that doesn't help, it's going to be a lot harder.

Increasing the CPU has no appreciable effect. On some other jobs on different MRs (which I failed to make a note of), this test finished a lot quicker, under 3 minutes, although still a few seconds slower than the next slowest test (usually one of the functional test jobs) - probably different AWS instances.

What we can easily do is move the job around in the YAML so it runs a bit earlier - I am not 100% sure but I think the first jobs will tend to pick up a kubernetes executor when it becomes available assuming the same requirements. Similarly, the legacy w3c job is very fast because it only runs a handful of tests, so we can run that last alongside unit tests. This doesn't affect the gitlab UI which is alphabetical, only the job execution order.

Whole test run in 5m7s https://git.drupalcode.org/project/drupal/-/pipelines/417753 - this may be a new record.

This is due to a fast test runner, but with that runner, the build test finished within a few seconds either side of the slowest functional tests, so having it just before or just after the functional tests seems right.

Wow!

Confirmed that the build jobs are not changed other than ordering. LTGM.

I think the IS needs an update, though.

Updated the issue summary, good point.

Realised one more thing. cspell is the slowest lint job, but it runs last.

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

4m 57s

!!!!!!!

LGTM.

4m 57s

Nice!

Amazing that we can still eke out a few more seconds with minor tweaks.

longwave → closed merge request !11130

4:57

What!?!

Truly incredible 🤩🤘

📌 Deprecate TestDiscovery test file scanning, use PHPUnit API instead Active is the next big one here I think in case anyone would like to see sub-5 minute runs more often.

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