Fix intermittent failure in ANSIOutput test... #4518
Merged
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.
This PR addresses #2734.
The issue was traced down to the
makeLines
helper function. Previously, this function would generate a set of test lines varying in length between 0 characters and 1024 characters. Sometimes, randomly, this would result in the last test line being 0 characters long. When this happened, the last line would be ignored byANSIOutput.processOutput
(as expected), resulting in a test failure like this:The fix was to ensure that the last line returned from the
makeLines
helper function is at least one character long so it won't get ignored byANSIOutput.processOutput
.Additionally, I fixed the
testOutputLines
function to use its arguments and I added in a call toensureNoDisposablesAreLeakedInTestSuite
, as required now.QA Notes
I was able to reproduce this issue locally by running thousands of iterations of the following test:
Which would result in a failure nearly 100% of the time. You can test this locally by adding the
for
loop to this this.