test: Increase initial RPC timeout to 60 seconds #11091
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
utACK ea1adc6726ed753db7737a6b8ab772c081037211 |
Contributor
|
utACK ea1adc6 |
Member
Contributor
|
utACK. I'm afk until Wednesday so I can't test, but this seems like a reasonable change. Slight preference for the variable names within the function to be lower case. |
When running the tests locally with a parallelism of 4 on an otherwise busy system, RPC can take quite a wait to come up. Change the timeout to 60 seconds just to be safe.
laanwj
force-pushed
the
2017_08_test_wait_for_rpc
branch
from
ea1adc6 to
c1470a0
Compare
Member
Author
|
ea1adc6 → c1470a0 only changed the case of the variables |
Member
|
utACK c1470a0 |
laanwj
added a commit
that referenced
this pull request
Aug 20, 2017
c1470a0 test: Increase initial RPC timeout to 60 seconds (Wladimir J. van der Laan) Pull request description: When running the tests locally with a parallelism of 4 on an otherwise busy system, RPC can take quite a wait to come up. With the current timeout tests often fail with "Unable to connect to bitcoind". Change the timeout to 60 seconds just to be safe. Tree-SHA512: 0c08cc8ce3f25ba2882beac2a50d1fcdd7c8c3bd6e3a8707813f94f2d39c14e2139ba1ddf7f9b66013d4c7f55db92d3f4aa88b433d855fd21e82842e350e459a
maflcko
pushed a commit
to maflcko/bitcoin-core
that referenced
this pull request
Oct 3, 2017
When running the tests locally with a parallelism of 4 on an otherwise busy system, RPC can take quite a wait to come up. Change the timeout to 60 seconds just to be safe. Github-Pull: bitcoin#11091 Rebased-From: c1470a0
codablock
pushed a commit
to codablock/dash
that referenced
this pull request
Sep 24, 2019
c1470a0 test: Increase initial RPC timeout to 60 seconds (Wladimir J. van der Laan) Pull request description: When running the tests locally with a parallelism of 4 on an otherwise busy system, RPC can take quite a wait to come up. With the current timeout tests often fail with "Unable to connect to bitcoind". Change the timeout to 60 seconds just to be safe. Tree-SHA512: 0c08cc8ce3f25ba2882beac2a50d1fcdd7c8c3bd6e3a8707813f94f2d39c14e2139ba1ddf7f9b66013d4c7f55db92d3f4aa88b433d855fd21e82842e350e459a
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
6 participants
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.
When running the tests locally with a parallelism of 4 on an otherwise busy system, RPC can take quite a wait to come up.
With the current timeout tests often fail with "Unable to connect to bitcoind".
Change the timeout to 60 seconds just to be safe.