Increase BDD Startup Timeout

There have been a number of instances of BDD tests which were
starting correctly but due to high load on the Jenkins host were
unable to complete prior to the timeout expiry.

This can been seen in action during
https://jenkins.hyperledger.org/view/fabric/job/fabric-verify-behave-x86_64/19/
in the chaincode authorizable counter test. Looking at the peer logs
it can be seen that peers vp1, vp2, and vp3 started up in 9, 1 and 5
seconds respectively. vp0 however timed out and didn't start.

Increasing the timeout from 10 to 20 seconds for peers to connect to
membersrvc and from 15 to 30 seconds overall to combat this.

Change-Id: I5c45697a63b95dd31371f423d274de69f0dc5cd3
Signed-off-by: Julian Carrivck <[email protected]>

Author: juliancarrivick-ibm

bddtests/scripts/start-peer.sh

@@ -2,7 +2,7 @@
 
 SCRIPT_DIR=$(dirname $0)
 MEMBERSHIP_IP=$(cat /etc/hosts | grep membersrvc | head -n 1 | cut -f1)
-TIMEOUT=10
+TIMEOUT=20
 
 if [ -n "$MEMBERSHIP_IP" ]; then
     echo "membersrvc detected, waiting for it before starting with a $TIMEOUT second timout"

bddtests/steps/peer_basic_impl.py

@@ -40,7 +40,7 @@ def step_impl(context, composeYamlFile):
 
     bdd_compose_util.parseComposeOutput(context)
 
-    timeoutSeconds = 15
+    timeoutSeconds = 30
     assert bdd_compose_util.allContainersAreReadyWithinTimeout(context, timeoutSeconds), \
         "Containers did not come up within {} seconds, aborting".format(timeoutSeconds)