Closed (fixed)
Project:
Drupal core
Version:
11.1.x-dev
Component:
phpunit
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
30 Apr 2025 at 15:27 UTC
Updated:
27 May 2025 at 18:09 UTC
Jump to comment: Most recent
Comments
Comment #2
catchComment #4
mondrakeNo brainer
Comment #5
catchFound some more Migrate tests we should add this to. What tends to happen is when tests are added removed, eventually it shuffles the ordering that ones which used to start at the beginning of the job by accident without explicitly being marked #slow end up starting later and finishing at or near the end of the job.
Comment #6
smustgrave commentedLGTM!
Comment #7
alexpottI wish we could just make PHPUnit responsible for this and remove #slow completely. It should just run the slowest tests from the last run first...
Committed and pushed bccd5a0c920 to 11.x and f2a221b3523 to 11.2.x and 00080f5aa17 to 11.1.x. Thanks!
Backported to 11.1.x as a test only change.
Comment #11
mondrakeI think we are close to be able to do that. IMO the hardest part is to consolidate test time results from the multiple spawns of run-test.sh and again from the multiple CI jobs. Good news is that a PoC to get a consolidated artifact with all the data seem to work in #3523614: [CI] Refactor DeprecationHandler in a standard PHPUnit extension, and collect deprecation statistics. Once that's in, we could build on that logic to do the same for test time results.