Skip to content

Commit

Permalink
FAB-2674: Failing behave bootstrap test
Browse files Browse the repository at this point in the history
Instantiating the proposal takes between 45-50
seconds, so the 30 second timeout needed to be
increased. The timeout was set at 90 to account
for different environments.

Note: this timeout is not the total amount of
time to wait, but an "upto 90 second" wait time.

Change-Id: I69beffa1c4e29512c5102753cbc2afa47225a496
Signed-off-by: Latitia M Haskins <latitia.haskins@gmail.com>
  • Loading branch information
lhaskins committed Mar 7, 2017
1 parent 30a0e21 commit 55fda40
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions bddtests/features/bootstrap.feature
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Feature: Bootstrap
As a blockchain entrepreneur
I want to bootstrap a new blockchain network

@doNotDecompose
#@doNotDecompose
@generateDocs
Scenario Outline: Bootstrap a development network with 4 peers (2 orgs) and 1 orderer (1 org), each having a single independent root of trust (No fabric-ca, just openssl)
#creates 1 self-signed key/cert pair per orderer organization
Expand Down Expand Up @@ -162,7 +162,7 @@ Feature: Bootstrap
# Under the covers, create a deployment spec, etc.
When user "dev0Org0" using cert alias "dev0Org0App1" creates a instantiate proposal "instantiateProposal1" for channel "com.acme.blockchain.jdoe.Channel1" using chaincode spec "cc_spec"

And user "dev0Org0" sends proposal "instantiateProposal1" to endorsers with timeout of "30" seconds with proposal responses "instantiateProposalResponses":
And user "dev0Org0" sends proposal "instantiateProposal1" to endorsers with timeout of "90" seconds with proposal responses "instantiateProposalResponses":
| Endorser |
| peer0 |
| peer2 |
Expand Down

0 comments on commit 55fda40

Please sign in to comment.