tests: General logs tests should use Sentry logs API #5262
Merged
+7
−8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sentrivana
changed the title
alexander-alderman-webb
approved these changes
Dec 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The Sentry Logs functionality is currently tested in three places:
test_logs.pyintegrations/loguru/test_loguru.pyintegrations/logging/test_logging.pyThe idea is that 1. checks the general Sentry logs feature, while 2. and 3. check the Sentry logs integration with logging/Loguru.
This PR changes the log calls in 1. to use the Sentry logs API directly (instead of the stdlib
loggingAPI) to make this distinction clearer.