[test] TreeDictionary.Keys: Remove stray print that’s flooding test output#370
Merged
lorentey merged 1 commit intoapple:release/1.1from May 29, 2024
Merged
Conversation
Member
Author
|
@swift-ci test |
Contributor
|
@lorentey Ahh… this is a good fix! Sorry about that one. Would these fixes happen enough that some kind of linter that automatically flags a diff with |
Member
Author
|
@vanvoorden Oh I didn't even remember this was a recent addition. This is not a big deal! And it's pretty easy to catch by looking through CI output -- which is how this one came to light. It can be legitimate for tests to print, and I don't think we want to develop a linter for this. We can simply catch these as they happen. |
Member
Author
|
Huh, this isn't ideal: This looks like a recent compiler regression. I'll look into it tomorrow. |
Member
Author
|
@swift-ci test |
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.
The
test_isEqual_exhaustivetest includes a stray print statement that is flooding test output with a myriad lines of useless data.Checklist