fix: correct assertion error messages in integer_test.cairo - #9047
Merged
orizi merged 1 commit intoDec 11, 2025
Merged
Conversation
|
This change is |
orizi
approved these changes
Dec 11, 2025
orizi
left a comment
Collaborator
There was a problem hiding this comment.
@orizi reviewed 1 of 1 files at r1, all commit messages.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on @strmfos)
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
3 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.
Fixed copy-paste error in integer comparison tests. The assertion checks
!(5 <= 4)but the error message incorrectly said'!(5 <= 8)'. Changed it to'!(5 <= 4)'to match the actual condition being tested. This was repeated across 6 integer types (u8, i8, i16, i32, i64, i128).