Downgrade 'Unable to find purge backend' messages to info #11899
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.
#11858 has made test output very noisy, because the
wagtail.contrib.frontend_cache
app is enabled inINSTALLED_APPS
but has no backends defined (by default - these are added for individual tests viaoverride_settings
) - consequently, any publish/unpublish action in the regular tests produces a warning "Unable to find purge backend for localhost".I've chosen to downgrade this to an "info" message, since warnings are generally reserved for configurations that are "wrong but recoverable" - there are potentially valid reasons to have a frontend cache configured for some but not all hostnames, so it's not inherently something that needs developer attention.