[JENKINS-71139] Alternate reproducer for NUL issue in SuiteResult.stdout
#520
Conversation
This file contains 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
jglick
commented
Apr 24, 2023
There was a problem hiding this comment.
$ od -a src/test/resources/hudson/tasks/junit/null-output.txt
0000000 f o o nul b a r
0000007
This was referenced Apr 24, 2023
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.
jenkinsci/jenkins#7875 but demonstrating how this can break JUnit test results when a test happens to print NUL characters in its standard output, depending on exactly how the report is structured. Passes against Jenkins 2.397, fails against 2.398—though, weirdly, in a different way than both the observed file load error and the core test failure: rather than the parsing failing with an error message, the
stdoutfield is simply quietly omitted (leftnull).