Problem/Motivation

Core unit tests (nearly) always finish last during the lint stage, we can speed them up a bit.

Before:
https://git.drupalcode.org/issue/drupal-3565258/-/jobs/7840322/viewer

Test run duration: 1 min 7

After:

https://git.drupalcode.org/issue/drupal-3565258/-/jobs/7840322/viewer

Test run duration: 51 sec

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Issue fork drupal-3565463

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

catch created an issue. See original summary.

catch opened merge request !14214

catch’s picture

catch
he/him
Primary language English
commented
Issue summary: View changes
mondrake’s picture

mondrake
Location 🇮🇹
commented
Related issues: +#3526459: Autodetect available CPUs in run-tests.sh for concurrency

I’d rather work towards #3526459: Autodetect available CPUs in run-tests.sh for concurrency. That will mean the cpu request will by itself define the concurrency based on the actual runner.

mondrake’s picture

mondrake
Location 🇮🇹
commented
Related issues: +#3515347: Reduce run-tests.sh complexity in spawning subprocesses

and BTW when combined with #3515347: Reduce run-tests.sh complexity in spawning subprocesses would take core unit test run duration to 15-20 seconds on a 71 concurrency

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.