Change libswoc test for undefined errno to a much higher number - #13531
Merged
Conversation
JosiahWI
approved these changes
Aug 11, 2026
bneradt
approved these changes
Aug 11, 2026
cmcfarlen
pushed a commit
that referenced
this pull request
Aug 12, 2026
libswoc tests include one that expects errno 134 to be unknown; this is no longer the case in Linux 7.2. This patch increases the errno to one that should be unknown for the forseeable future. (cherry picked from commit a2009d7)
Contributor
|
Cherry-picked to the 10.2.x branch as 5e81c3a for the 10.2.0 release. |
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
4 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.
libswoc tests include one that expects errno 134 to be unknown; this is no longer the case in Linux 7.2. This patch increases the errno to one that should be unknown for the forseeable future.