Problem/Motivation
Tests take over 20 minutes to complete.
Steps to reproduce
Proposed resolution
https://git.drupalcode.org/project/gitlab_templates/-/blob/main/docs/job...
Not certain if this is compatible with everything (e.g. coverage), but giving it a try.
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork crm-3557793
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:
Comments
Comment #2
jdleonardComment #4
jdleonardDon't think I'm going to figure out how to maintain code coverage reporting while parallelizing. However, apparently it has been done.
Possible inspiration: https://git.drupalcode.org/project/distributions_recipes/-/merge_request...
Or I read that XDebug's coverage mode is worth considering.
Comment #5
bluegeek9 commentedCode coverage cannot have concurrent tests. It is a limitation. Only the code coverage job is not using concurrency.
Comment #7
jdleonardhttps://github.com/paratestphp/paratest states as a benefit: "Code Coverage report combining. Run your tests in N parallel processes and all the code coverage output will be combined into one report."
This suggests that someone got it working: https://www.drupal.org/project/distributions_recipes/issues/3442014#comm...
I'll ping alexdmccabe and see if he's willing to give it a stab.