Remove XFAIL from tests for 'bug' 48770 #5386
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug 48770 was opened due to conflicting expectations about the behavior of:
The one reporting the 'bug' seemed to think that since the method name was prefixed with
parent::
, it should call the method in the superclass of the class where this code appears.However,
$this
might be an instance of a subclass. If so, then it is quite reasonable thatcall_user_func_array
will call the method as defined in the superclass of the receiver.So the 'bug' is not really a bug. Therefore, there is no need for an XFAIL in the tests. They
should just pass.
Amend tests to reflect the actual expected behavior of
call_user_func_array
, not what theperson who reported bug 48770 thought it should be.
The fact that the PHP interpreter crashes with an error message on the test code is not
really an issue either. The test code is essentially no different from:
If anything, perhaps the error message which PHP displays on a stack overflow could be
improved.