- Issue created by @catch
- Status changed to Needs review
7 months ago 11:15am 25 May 2024 - Status changed to RTBC
7 months ago 2:54pm 27 May 2024 - 🇺🇸United States smustgrave
This will have no effect on core test runs, so ideally we'd see how much difference it makes with a contrib module that has a decent test suite like paragraphs.
So seems like one of those features that may have to be merged first to truly measure impact right?
- 🇨🇭Switzerland berdir Switzerland
I think it would be possible to create a merge request in a module like webform or paragraphs and apply the core patch and verify the output/execution time before/after. But we can also do that after this was merged.
- 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
Committed to 11.x and backported to 11.0.x, 10.4.x and 10.3.x
Also backported to 10.2.x even though technically this is a task because for contrib modules testing this, they will still be using the 10.2.x checkout for some time. If folks disagree with that, happy to wind that back.
- Status changed to Fixed
7 months ago 9:47pm 28 May 2024 -
larowlan →
committed 3956262a on 10.2.x
Issue #3449743 by catch: Try to optimize test ordering when run-tests.sh...
-
larowlan →
committed 3956262a on 10.2.x
-
larowlan →
committed 40b02150 on 10.3.x
Issue #3449743 by catch: Try to optimize test ordering when run-tests.sh...
-
larowlan →
committed 40b02150 on 10.3.x
-
larowlan →
committed 463ffc70 on 10.4.x
Issue #3449743 by catch: Try to optimize test ordering when run-tests.sh...
-
larowlan →
committed 463ffc70 on 10.4.x
-
larowlan →
committed 0749ca2e on 11.0.x
Issue #3449743 by catch: Try to optimize test ordering when run-tests.sh...
-
larowlan →
committed 0749ca2e on 11.0.x
-
larowlan →
committed 17ec849e on 11.x
Issue #3449743 by catch: Try to optimize test ordering when run-tests.sh...
-
larowlan →
committed 17ec849e on 11.x
Automatically closed - issue fixed for 2 weeks with no activity.