Fix logging in functional tests in case of connection failure #4006
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.
Summary
As of #3932, if a functional test fails to establish a DB connection on setup (e.g. due to invalid configuration), it fails like this:
The expected behavior is:
The reason is that we no longer check
if (isset($this->sqlLoggerStack->queries)
because$sqlLoggerStack
is of typeDebugStack
and it's assumed that the$queries
property is always set. Although, in the case of a connection failure, the logger is not initialized.The solution is to initialize the logger before trying to connect.