Make fuzz_threaded_connections
more robust
#2074
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.
In
fuzz_threaded_connections
, if one thread is being run while another is starved, and the running thread manages to calltimer_tick_ocurred
twice after the starved thread constructs the inbound connection but before it delivers the first bytes, we'll receive an immediate error andunwrap
it, causing failure.The fix is trivial, simply remove the unwrap and return if we're already disconnected when we do the initial read.
While we're here, we also reduce the frequency of the
timer_tick_ocurred
calls to give us a chance to occasionally deliver some additional messages.Fixes #2073