Bump Max Log Count in Tests#6901
Merged
Merged
Conversation
ajpallares
approved these changes
Jun 3, 2026
This was referenced Jun 3, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
The
record-and-push-paywall-template-screenshotsjob is failing in main because we've exceeded the max log count:This PR bumps the max log count from 1k to 10k to attempt to alleviate this issue.
Note
Low Risk
Test-only logging limit change with no impact on app runtime, security, or data handling.
Overview
Raises the per-test log buffer on the shared UI test base class from 1,000 to 10,000 messages so verbose flows (e.g. paywall validation screenshot tests) no longer trip the “max messages stored / likely leak” guard in CI.
Reviewed by Cursor Bugbot for commit 81bf1ac. Bugbot is set up for automated code reviews on this repo. Configure here.