[ci][rabbitmq] Increase wait timeout #3022
Merged
Conversation
This file contains 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
olivielpeau
force-pushed
the
olivielpeau/rabbitmq-ci-increase-timeout
branch
5 times, most recently
from
917b28a to
64d5219
Compare
Rabbitmq can take a long time to start up on the Travis environment (can take from 1sec to more than 30sec from what I've found), and unfortunately I went through rabbitmq's logs and haven't found any obvious explanation for that. Let's just increase the timeout instead of having the test fail every other build.
olivielpeau
force-pushed
the
olivielpeau/rabbitmq-ci-increase-timeout
branch
from
64d5219 to
8b1ec35
Compare
degemer
added a commit
that referenced
this pull request
Nov 15, 2016
* master: (254 commits) Reduce the maximum amount of argument to pylint. [forwarder] stop flushing after 10s [etcd] Report errors connecting to etcd endpoint (#3007) Postfix check should pass raise_on_empty_output=False [status] Silence requests exception [psutil] Only set `psutil.PROCFS_PATH` once in the collector (#3013) [ci] fix check name detection of test files (#3021) [ci][rabbitmq] Increase wait timeout (#3022) [core] SpooledTemporaryFile for subprocess output (#3002) [collector] isolate system checks (#3001) [ci] Fix Travis jobs timing out (#3017) [mongo] Use db.current_op instead of manually querying (#3016) [ci] fix bad citizens detection (#3020) [ci] add debug logs (#3019) [mongo] use `currentOp` for mongodb 3.2+ Use proxy for API key check in info page (#3012) [mongo] Add MongoDB 3.2 support [mongo] Add MongoDB 3.2 to travis-ci config [packaging] 5.11.0 nightlies (#3009) [core] hard-deprecate start/stop/restart/status (#3004) ...
truthbk
pushed a commit
that referenced
this pull request
Nov 16, 2016
Rabbitmq can take a long time to start up on the Travis environment (can take from 1sec to more than 30sec from what I've found), and unfortunately I went through rabbitmq's logs and haven't found any obvious explanation for that. Let's just increase the timeout instead of having the test fail every other build.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rabbitmq can take a long time to start up on the Travis environment
(can take from 1sec to more than 30sec from what I've found), and
unfortunately I went through rabbitmq's logs and haven't found any
obvious explanation for that.
Let's just increase the timeout instead of having the test fail every
other build.