Problem/Motivation
Functional test jobs are nearly consistently under four minutes, which means kernel tests are now running longer. The jobs were more even than this previously, but as tests are added things move around, and it's as much about the distribution of tests as any individual test.
Before:
https://git.drupalcode.org/project/drupal/-/jobs/2177702 4m9s
https://git.drupalcode.org/project/drupal/-/jobs/2177703 5m13s
https://git.drupalcode.org/project/drupal/-/jobs/2177704 2m23s
After:
https://git.drupalcode.org/project/drupal/-/jobs/2193124 3 min 18 sec
https://git.drupalcode.org/project/drupal/-/jobs/2193125 2 min 55 sec
https://git.drupalcode.org/project/drupal/-/jobs/2193126 2 min 18 sec
Generally precision isn't massively important here - we can just add @group #slow to a few tests with 20+ test methods, and those generally take 20-30 seconds to run instead of 1-3 seconds for a single method test. The group slow logic will then distribute those tests equally among the three runners, and hopefully we'll end up with three jobs at least than four minutes each.
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
Issue fork drupal-3462759
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 #3
catchComment #4
catchHere we go:
https://git.drupalcode.org/project/drupal/-/jobs/2177925 3m3s
https://git.drupalcode.org/project/drupal/-/jobs/2177926 2m54s
https://git.drupalcode.org/project/drupal/-/jobs/2177927 2m13s
Comment #5
catchComment #6
catchComment #7
smustgrave commentedSeems straight forward.
Comment #8
catchAdd 'after' numbers to the issue summary from the latest run: https://git.drupalcode.org/project/drupal/-/pipelines/230965
Comment #13
longwaveCommitted and pushed afce6da313 to 11.x and e8d874f4db to 11.0.x and b9c8018c12 to 10.4.x and 32075e1a5f to 10.3.x. Thanks!