- Issue created by @mondrake
- Assigned to mondrake
- Status changed to Needs review
2 months ago 9:07pm 24 May 2025 - 🇺🇸United States smustgrave
Appears to have merge conflicts
If you are another contributor eager to jump in, please allow the previous poster(s) at least 48 hours to respond to feedback first, so they have the opportunity to finish what they started!
- 🇮🇹Italy mondrake 🇮🇹
Yes needs waiting for https://www.drupal.org/project/drupal/issues/3497431 📌 Deprecate TestDiscovery test file scanning, use PHPUnit API instead Active
- 🇮🇹Italy mondrake 🇮🇹
#16 this is refactoring internal code, and no outside effects are expected. The only suggestion I would have is to compare test result logs from run-tests.sh, in core and contrib, before and after the change. They should be the same.
- 🇺🇸United States smustgrave
left a comment on the MR but leaving in review for additional eyes,
- 🇮🇹Italy mondrake 🇮🇹
Since run-tests.sh is no longer spawning subprocesses of run-tests.sh itself, we no longer need to persist the test result SQLite database on disk to allow parent-child processing. So, we can try using a
:memory:SQLite database within the main run-tests.sh process. - Issue was unassigned.
- Status changed to Needs work
12 days ago 12:00pm 24 July 2025 The Needs Review Queue Bot → tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.