Closed markdwhite closed 1 year ago
You have found a problem in the PHP runtime that leads to a segmentation fault. An issue like this has to be reported here using a minimal, self-contained, reproducing test case.
Please note that a test case that needs to be run through PHPUnit does not qualify as either "minimal" or "self-contained" when reporting bugs for the PHP runtime. Best practices for reporting bugs in PHP are documented here.
Summary
This is possibly a misunderstanding of correct implementation of new Event System
After refactoring of a test extension from PHPUnit 9 to PHPUnit 10, tests run successfully as expected. With JUnit output logging enabled the junit.xml is produced correctly. With Xdebug enabled and JUnit output logging disabled, all tests run as expected. With Xdebug enabled and JUnit output logging enabled, all tests run correctly and the junit.xml is produced correctly but a segfault is reported. With Xdebug enabled and JUnit output logging enabled, but the extension is removed from phpunit.xml, tests fail, but junit.xml is correct and there is no seg fault.
Current behavior
In PHPUnit 9, the following approach was used successfully to override "final" class designations to simplify testing:
phpunit.xml (extract):
BypassFinalHook.php
With PHPUnit 10 this has been rewritten as:
phpunit.xml (extract):
BypassFinalHook.php:
BeforeTestMethodCalledSubscriber.php:
Output when xdebug and junit logging enable:
There is no core dump in /var/crash to provide, though I'll do this if you tell me how to obtain a core dump.
composer info | sort:
How to reproduce
Not sure. This may be down to incorrect implementation of the Event System by me.
Expected behavior
Execution without segfault.