Stripping success result in order to speed up transmit in distributed test mode #6410
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.
Stripping success result in order to speed up transmit in distributed test mode
Description
If the result is successful, fulfill SIZE information in BODY/HEADER etc, and replace DATA information with NULL. So the result could be smaller than it was.
Motivation and Context
When doing test in distributed mode, each Server will send its result back to Client. If the result size is big and the number of results is big too, it will take time to finish results transmition. Even we find that sometimes when test has already finished, STOP singal has been sent from Client to Servers, both Client and Servers cannot exit because result transmition was still undergoing whitch bocked Client and Servers from exting.
If a test result is FAILED, we do need its complete DATA information to do debug after test, we will not strip the result itself. But on the other hand, if a test result is SUCCESSFUL, we need only its SIZE to do static after test, we can trim all the DATA from BODY/HEADER etc.
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: