bug #31382 [PhpunitBridge] Fix not unserialized logs after DeprecationErrorHandler refacto (l-vo)
This PR was merged into the 4.3-dev branch.
Discussion
----------
[PhpunitBridge] Fix not unserialized logs after DeprecationErrorHandler refacto
| Q | A
| ------------- | ---
| Branch? | master
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets |
| License | MIT
| Doc PR |
During the refactoring for #29211 , it seems a little bug was introduced. When using runInSeparateProcess, deprecation message isn't unserialized anymore.
Commits
-------
f522729527
[PhpunitBridge] Fix not unserialized logs after DeprecationErrorHandler refactoring
This commit is contained in:
commit
c315767b69
@ -133,6 +133,7 @@ class DeprecationErrorHandler
|
||||
if ($deprecation->originatesFromAnObject()) {
|
||||
$class = $deprecation->originatingClass();
|
||||
$method = $deprecation->originatingMethod();
|
||||
$msg = $deprecation->getMessage();
|
||||
|
||||
if (0 !== error_reporting()) {
|
||||
$group = 'unsilenced';
|
||||
|
@ -133,6 +133,11 @@ class Deprecation
|
||||
return $this->originMethod;
|
||||
}
|
||||
|
||||
public function getMessage(): string
|
||||
{
|
||||
return $this->message;
|
||||
}
|
||||
|
||||
/**
|
||||
* @param string $utilPrefix
|
||||
*
|
||||
|
Reference in New Issue
Block a user