No delay of Client final interval report#2025
Open
davidBar-On wants to merge 2 commits intoesnet:masterfrom
Open
No delay of Client final interval report#2025davidBar-On wants to merge 2 commits intoesnet:masterfrom
davidBar-On wants to merge 2 commits intoesnet:masterfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Version of iperf3 (or development branch, such as
masteror3.1-STABLE) to which this pull request applies:master 3.21+
Issues fixed (if any): Final interval report always delayed until result exchange #2019
Brief description of code changes (suitable for use as a commit message):
Print final interval report from Client on
TEST_END(like the Server) instead ofDISPLAY_RESULTS. This is to prevent the problem that the last Client's interval report is delayed on high-latency links (like cellular systems).