Prevent test suite lockups on test server failure #758
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 addresses two issues:
When the test server fails for whatever reason, the test suite gets stuck in infinite loop reading stderr output. This can be simply prevented, because when the
gets
reads from closed pipe, it returnsnil
.When the test server fails during startup, there is no way to know why. Therefore the server messages are collected and reported in case the stderr pipe is unexpectedly closed.
Original behavior:
where the process infinitely loops here:
excon/tests/test_helper.rb
Lines 247 to 251 in b64de99
New behavior: