- Issue created by @mondrake
- ๐ฎ๐นItaly mondrake ๐ฎ๐น
MR implements option 1 from the issue summary. IMHO option 2 is overkill and 3 is complicated and risk regressions easily.
- ๐ฌ๐งUnited Kingdom catch
Yeah only for the default PHP version sounds good to me too.
- ๐บ๐ธUnited States smustgrave
Assuming this will have to be tweaked when https://www.drupal.org/project/drupal/issues/3515706 ๐ Switch the default test environment to PHP 8.4 Active lands?
- ๐บ๐ธUnited States smustgrave
Didn't mean to change status but if 8.4 is a default won't this change need to apply to 8.4
- ๐ฎ๐นItaly mondrake ๐ฎ๐น
Ah! No itโs already for 8.4, check the MR - 8.3 and 8.5 are getting the โno-coverageโ job settings. Anyway this is about components unit tests which are getting rather independent as we speak.
- ๐ฎ๐นItaly mondrake ๐ฎ๐น
Sorry, I found opportunities to remove duplication
- ๐ฎ๐นItaly mondrake ๐ฎ๐น
Adjusted post- ๐ฑ [meta] Support PHPUnit 11 in Drupal 10 Postponed .
Letting PHPUnit's own deprecations fail the job execution on PHPUnit 8.5 as the purpose of that job is precisely to shout out when language deprecation or changes occur in this stage of PHP development, so I thought it is a good spot where to let PHPUnit shout as well.
With the
PHPUNIT_FAIL_ON_PHPUNIT_DEPRECATION
job variable it's a piece of cake to silence them if we do not manage to solve them before PHP 8.5 is released.