Repository navigation
tests: allow custom realm notice on stderr - #1181
Merged
ffumero2003 merged 2 commits intoOct 1, 2026
Merged
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
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.
Summary
Using http(s)://…notice in integration-test stderrtest/unit/test_console_tool.py)When
B2_ENVIRONMENTis a custom URL, the CLI prints aUsing <url>notice to stderr; the integration suite's sharedshould_succeedasserted clean stderr, so every command erroring on that notice (55 errors when the suite is retargeted to a simulator). This narrows the allow-list to that one notice, mirroring the regex the unit tests already use. No CLI runtime behavior changes.Verification
Unexpected stderr line: 'Using http://…'errors are goneNote
Same change as #1180 (which merged into
development); this is the master-targeted PR.