Spin off from #3526459: Autodetect available CPUs in run-tests.sh for concurrency
A few unit tests are executing in way more time than average unit tests, especially if they're executed in isolation.
These are making a hard tail on the unit test job in the pipeline.
#slow group for some unit tests so the slowest ones remaining are started first.
Show commandsStart 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:
changes, plain diff MR !15720
Comments
Comment #3
mondrakeComment #4
mondrakeComment #5
mondrakeComment #6
catchNot entirely sure about this one because from discussion in slack, it sounds like the longest running unit tests are around 10-12 seconds and also the fastest run for all unit tests is around 10-12 seconds. So this prevents us going below 10-12 seconds but that's already faster than all of the lint jobs that we also block other test jobs on like phpcs and phpstan.
Comment #7
alexpottThis does not feel like the right thing to do. Unit tests should remain unit tests - making them kernel just because of test suite performance and not for capabilities they require is surprising and would be hard to explain. Also I'm sure that individually these tests will now take longer.
Comment #8
mondrakeOK, makes sense.