Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase Net::HTTP / rest-client open_timeout #1470

Merged
merged 1 commit into from
Feb 13, 2018
Merged

Conversation

rhass
Copy link
Contributor

@rhass rhass commented Feb 13, 2018

Starting with Ruby v2.3.0 the default value for open_timeout changed from nil (disabled) to 60 seconds. This 60 second value remains in current released versions of Ruby which is why we continue to see this behavior in newer versions as well.

  • Ruby cset in which the open_timeout default value was introduced: ruby/ruby@52e1c3b

This caused periodic test failures which were observed and documented when we originally moved from Ruby v2.2.6 to v2.3.3.

More recently these timeouts have caused increase of erratic test failures on both TravisCI and internal Jenkins build for slower platforms. Rather than setting an open_timeout value of nil and disabling the
open_timeout entirely I have chosen to set a 300 second timeout as a starting point for increasing the timeout value to allow for legitimate timeouts to occur rather than having test jobs get stuck indefinitely.

Signed-off-by: Ryan Hass [email protected]

Starting with Ruby v2.3.0 the default value for `open_timeout` changed
from `nil` (disabled) to `60` seconds. This 60 second value remains in
current released versions of Ruby which is why we continue to see this
behavior in newer versions as well.

  ruby/ruby@52e1c3b

This caused periodic test failures which were observed and documented
when we originally moved from Ruby v2.2.6 to v2.3.3.

  e7a2ac8

More recently these timeouts have caused increase of erratic test
failures on both TravisCI and internal Jenkins build for slower
platforms. Rather than setting an `open_timeout` value of `nil` and
disabling the `open_timeout` entirely I have chosen to set a 300 second
timeout as a starting point for increasing the timeout value to allow
for legitimate timeouts to occur rather than having test jobs get
stuck indefinitely.

Signed-off-by: Ryan Hass <[email protected]>
@rhass rhass requested review from a team and scotthain February 13, 2018 00:18
Copy link

@scotthain scotthain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice detective work!

@rhass
Copy link
Contributor Author

rhass commented Feb 13, 2018

Special to thanks to @stevendanna for pointing out e7a2ac8 -- I wouldn't have found this without his help! =)

Copy link
Contributor

@stevendanna stevendanna left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Internally, let's make a card somewhere for investigating how in the world we would be hitting a 60 second timeout for open()? But, regardless of that, it makes sense to timeout opens and it makes sense to get the build working.

@rhass rhass merged commit ab4a553 into master Feb 13, 2018
@rhass rhass deleted the rhass/fix-timeout-issues branch February 13, 2018 17:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants