test: only assert on first lines of TLS trace#28043
Closed
Uh oh!
There was an error while loading. Please reload this page.
Conversation
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
The TLS trace data is best-effort, and enough can be dropped from pipe buffers that only the start of the trace is detected. Only assert on the first line of the trace, it should not get dropped, and it's enough to check that trace was enabled via CLI.
ContributorAuthor
sam-github commented Jun 3, 2019
From #27636, it looks like not enough of the data is piped to get to the first "Received Record", so lets just assert on the first line of trace output. Any trace output at all is enough to know that the CLI option had the expected effect. |
Collaborator
nodejs-github-bot commented Jun 3, 2019
lpinca approved these changes Jun 3, 2019
cjihrig approved these changes Jun 3, 2019
richardlau approved these changes Jun 3, 2019
BridgeAR approved these changes Jun 4, 2019
Collaborator
nodejs-github-bot commented Jun 4, 2019
Collaborator
nodejs-github-bot commented Jun 4, 2019
Collaborator
nodejs-github-bot commented Jun 5, 2019
Collaborator
nodejs-github-bot commented Jun 6, 2019
Collaborator
nodejs-github-bot commented Jun 6, 2019
ContributorAuthor
sam-github commented Jun 6, 2019
Landed in 2976bbd |
BridgeAR pushed a commit that referenced this pull request Jun 17, 2019
The TLS trace data is best-effort, and enough can be dropped from pipe buffers that only the start of the trace is detected. Only assert on the first line of the trace, it should not get dropped, and it's enough to check that trace was enabled via CLI. PR-URL: #28043Fixes: #27636 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
Merged
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
6 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.
The TLS trace data is best-effort, and enough can be dropped from pipe
buffers that only the start of the trace is detected. Only assert on the
first line of the trace, it should not get dropped, and it's enough to
check that trace was enabled via CLI.
Fixes: #27636
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes