Re-enable timeout tests on Travis + other fixes #2415
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.
What started out as a simple re-enabling of
tests/test-timeout.js
on Travis has turned into more cleanup and fixes along the way.If you want any of these commits parted out into separate PRs, let me know.
I have tested these commits on Travis many times now and each time all 4 node targets have been green, so I am fairly confident not only about
tests/test-timeout.js
, but also flaky tests intests/test-pipes.js
, and other random failures.One possibly "major" change included here is the change in timeout behavior. IMHO the timeout changes (in request.js) I've provided here more accurately reflect the intended behavior.