PHPUnit warning: Test code or tested code did not remove its own exception handlers

[nunomaduro]

Laravel Version

Any that uses PHPUnit ^10

PHP Version

Any

Database Driver & Version

No response

Description

Seems that, since PHPUnit 10.5.4, running any kind of test suite that boots the Laravel Framework displays the following warning multiple times: Test code or tested code did not remove its own exception handlers.

Steps To Reproduce

laravel new laravel
cd laravel
./vendor/bin/phpunit

[nunomaduro]

PHPUnit change that introduced this BC issue: sebastianbergmann/phpunit#5619.

[rikvdh]

@nunomaduro Shouldnt this be reported upstream as a regression?

[nunomaduro]

@rikvdh It's done. Sebastian is considering reverting it.

[nunomaduro]

Reverted. Problem solved.

[arderyp]

I never had this issue in 10.x, but I just upgraded from latest 10.x to latest 11.x and 11.0.4 and I'm seeing this on every single test in my project

[TomBerkGH]

I never had this issue in 10.x, but I just upgraded from latest 10.x to latest 11.x and 11.0.4 and I'm seeing this on every single test in my project

i get the same error since laravel update. PHPUnit 11.0.9 and Laravel 11.2.0

[elb98rm]

I can confirm this has reappeared:

• L11 : 11.2.0
• PHPUnit : 11.1.1

Looks like it's been re-introduced.

[oceanapplications]

I can confirm this has reappeared:

• L11 : 11.2.0
• PHPUnit : 11.1.1

Looks like it's been re-introduced.

Yup, Sebastian said it would be reintroduced in 11. What's the current work around other than using older phpunit?

[arderyp]

@oceanapplications various workarounds are presented in the Symfony thread: symfony/symfony#53812 (comment)

[phily245]

Putting the below in (what would be) my Tests/TestCase worked in the package I am working on and encountered this in:

public function tearDown(): void
{
    parent::tearDown();

    restore_error_handler();
    restore_exception_handler();
}

[zoispag]

We updated to L11 last week and today Dependabot bumped PHPUnit to v11 and these errors starting to appear for all tests:

• Test code or tested code removed error handlers other than its own
• Test code or tested code removed exception handlers other than its own

As of now, we can't find any working solution. This issue points to Symfony thread which is still open and redirects back to #49622. Does anyone have a working solution? @phily245 suggestion didn't do the trick :(

[JustChapman]

We have been digging into this issue at work with a new project. My boss found that removing newRelic in the docker container solved resolved the "Test code or tested code removed..." errors. He also mentioned there appears to be a memory leak in PHPUnit 11.3, though that has not yet been confirmed. I can confirm on my instance, removing newRelic from the docker container did resolve issues for me. Tests execute as expected now.

[lsfiege]

We have been digging into this issue at work with a new project. My boss found that removing newRelic in the docker container solved resolved the "Test code or tested code removed..." errors. He also mentioned there appears to be a memory leak in PHPUnit 11.3, though that has not yet been confirmed. I can confirm on my instance, removing newRelic from the docker container did resolve issues for me. Tests execute as expected now.

I also confirm, removing new relic from my docker container fixed this. But I can't confirm the phpunit memory leak

[eddyger]

Reading the phpunit documentation, we can find the #[WithoutErrorHandler] attribute mention on your test method. Using this attribute fix the "risky" message.