-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Process isolation doesn't work starting from 10.2.0 #5595
Comments
Thank you for your report. Please provide a minimal, self-contained, reproducing test case that shows the problem you are reporting. Without such a minimal, self-contained, reproducing test case I will not be able to investigate this issue. |
It looks it's a Laravel issue, since I have no problems when extending PHPUnit's |
@l-alexandrov Were you able to solve it? Please share it how ? |
@arclw In my case I'm using Laravel and it seems this is a feature that Laravel doesn't support. Reference: laravel/framework#49237 (comment) |
Does anyone know how to begin to debug this? I've tried adding the --debug flag to phpunit and it is not producing anything useful. This is definitely related to Laravel, but they do not have any desire to resolve the issue on PHP 8.3. The stdout is returning an empty string within |
The problem is not with PHPUnit itself. I have tried the annotation |
Signed-off-by: Natsuki Ikeguchi <[email protected]>
Signed-off-by: Natsuki Ikeguchi <[email protected]>
Signed-off-by: Natsuki Ikeguchi <[email protected]>
Summary
When enable processs isolation in any form (CLI argument, PHP doc annotation or attribute in
phpunit.xml
) the tests are failing with an error.I'm using PHPUnit in combination with Laravel 10.34.2. Prior to PHPUnit 10.2.0 I had no issues with proccess isolation.
Current behavior
When run a test in a process isolation I get
Test was run in child process and ended unexpectedly
error.How to reproduce
vendor/bin/phpunit --process-isolation
and see the error.Expected behavior
Getting no errors.
Configuration
The text was updated successfully, but these errors were encountered: