dump() no longer produces output in PHPUnit tests running under PHP 8.3

If we can accept dump() to write to STDERR, this seems easy to fix.

If this is just targetting D11, which requires 8.3, don't see an issue with the change.

This should be backported given that developers will also run tests on PHP 8.3 on Drupal 10.

Unsure if it's worth a change record, 99% will not notice the difference, the only thing I can see it affecting is if someone is redirecting output in a shell script or similar?

I don't think this is worth a change record, if someone turns out to be affected by this, they're unlikely to find out via the change record anyway I would think.

Later when we will have let PHPUnit 9 go, we may consider doing this differently, capturing the dump in a cache and actually printing it as part of the end test event, when the test is actually closed. Instead of using the STD streams that (both OUT and ERR), quite understandably, PHPUnit wants to advocate as part of the SUT, and therefore not mix with test code. At that point yes, a CR would do. But, please, PHPUnit 10+… I wouldn’t tamper with long dead listeners.

Committed and pushed 80139bdb8e to 11.x and 5e7ac12c4d to 10.3.x. Thanks!

I think we should backport this to 10.2 because it's really annoying and I'm not really sure there is a bc impact. Relying on the output of dump() feels v wrong.

Filed 📌 [PHPUnit 10+ only] Make dump() output in tests no longer use standard streams Needs review for follow up.

Agreed, backported to 10.2.x as this is tests-only and solves a PHP compatibility issue.

Automatically closed - issue fixed for 2 weeks with no activity.

mondrake → closed merge request !7114