Problem/Motivation

Try to see if "paratest" package would be suitable for core.
Related work:
* Contrib: #3370952: Run phpunit tests from a single job in parallel, using paratest
* Core: #2781123: [experiment] Explore paratest to run our phpunit tests in parallel

Issue fork gitlab_ci_testbed_for_drupal_core-3374070

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

fjgarlin created an issue. See original summary.

fjgarlin opened merge request !4

fjgarlin closed merge request !4

fjgarlin’s picture

fjgarlin commented

I tested "paratest" as an alternative to run the tests for each suite.

Results:

* Apache with concurrency: https://git.drupalcode.org/project/gitlab_ci_testbed_for_drupal_core/-/p...
90 mins total, fails in "Functional" and "Functional Javascript".

* Paratest: https://git.drupalcode.org/project/gitlab_ci_testbed_for_drupal_core/-/p...
126 mins total, fails same as the above AND phpunit, kernel.

While "paratest" made a significant improvement in running plain phpunit jobs in the contrib space, it does not seem to make a dent in core, which seems to be well optimized to leverage the concurrency capabilities of the dockerhub image used and apache. I was expecting a bigger margin of difference, but in this case it seems to be even slower, or at least, less efficient.

I won't pursue any further this task unless I am asked to.

fjgarlin reopened merge request !4

fjgarlin closed merge request !4

fjgarlin’s picture

fjgarlin commented
Status: Active » Fixed

Comparing times per job, paratest is still slower in every category.
Closing this issue as the investigation is done.

Status: Fixed » Closed (fixed)

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