- Issue created by @mondrake
- 🇬🇧United Kingdom catch
The disconnect between paratest and run-tests.sh timings looked a bit too much, so I checked phpunit test timings in HEAD and found bugs in the run-tests.sh logic (recently introduced by me).
📌 Try a shorter polling time in run-tests.sh Active is the issue.
https://git.drupalcode.org/project/drupal/-/jobs/2938499 reports 42 seconds to run tests now so a better baseline for comparison.
- 🇬🇧United Kingdom alexpott 🇪🇺🌍
Also, in the past when I've used paratest on projects I've had problems with deprecation testing and how Symfony adds the info. Maybe with the recent PHPUnit / Symfony PHPUnit Bridge changes this is no longer a problem but we need to confirm whether deprecation fails are still reported correctly - both that the test fails and that we can see the deprecation that causes the fail.
- 🇮🇹Italy mondrake 🇮🇹
plain PHPUnit: 1 min 54 secs
paratest: 24 secs
run-tests: 31 secs