-
-
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
Code paths that create a PHPUnit_Framework_Warning end up serializing/unserializing globals unconditionally #7
Comments
Closed by 12713ff. |
igorw
pushed a commit
to igorw-forks/phpunit
that referenced
this issue
Aug 24, 2011
glensc
pushed a commit
to glensc/php-phpunit
that referenced
this issue
Oct 4, 2022
Closed
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When PHPUnit is given a file with no test methods, with private test methods, with no public constructor, etc., it creates a PHPUnit_Framework_Warning object and "runs" it. Since this object has $backupGlobals === NULL, "running" it results in all the globals being serialized and then unserialized. In our environment there are globals that cannot be serialized, so this behavior breaks things and causes subsequent tests in the same suite to fail. So there needs to be a way to turn this behavior off. My suggestion is to have this behavior always be off by adding
to the PHPUnit_Framework_Warning class.
The text was updated successfully, but these errors were encountered: