Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

clarify test 160 #1331

Merged
merged 1 commit into from
Aug 19, 2015
Merged

clarify test 160 #1331

merged 1 commit into from
Aug 19, 2015

Conversation

bboreham
Copy link
Contributor

The point of the last few lines of test 160 is to see whether starting weave in a state where it thinks it should talk to a currently-stopped peer will hang it. This change makes this clearer (but does not run the launch command in a timeout wrapper because weave_on is a shell function and it's too complicated to extract it out for timeout to call).

weave_on $HOST2 launch-router
# Introduce host3 to remember the IPAM CRDT when we stop host2
weave_on $HOST3 launch-router $HOST2
stop_router_on $HOST2
weave_on $HOST1 launch-router $HOST3
assert_raises "DOCKER_HOST=tcp://$HOST1:$DOCKER_PORT timeout 30 $WEAVE launch-router $HOST3"

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.

@rade rade changed the title Explicitly check for hang on weave launch in test 160 clarify test 160 Aug 19, 2015
rade added a commit that referenced this pull request Aug 19, 2015
@rade rade merged commit f080e5a into master Aug 19, 2015
@rade rade deleted the clarify-test-160 branch August 19, 2015 20:32
@rade rade modified the milestone: 1.1.0 Aug 29, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants