Skip to content

Commit 55fda40

Browse files
committed
FAB-2674: Failing behave bootstrap test
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 <[email protected]>
1 parent 30a0e21 commit 55fda40

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

bddtests/features/bootstrap.feature

+2-2
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Feature: Bootstrap
1111
As a blockchain entrepreneur
1212
I want to bootstrap a new blockchain network
1313

14-
@doNotDecompose
14+
#@doNotDecompose
1515
@generateDocs
1616
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)
1717
#creates 1 self-signed key/cert pair per orderer organization
@@ -162,7 +162,7 @@ Feature: Bootstrap
162162
# Under the covers, create a deployment spec, etc.
163163
When user "dev0Org0" using cert alias "dev0Org0App1" creates a instantiate proposal "instantiateProposal1" for channel "com.acme.blockchain.jdoe.Channel1" using chaincode spec "cc_spec"
164164

165-
And user "dev0Org0" sends proposal "instantiateProposal1" to endorsers with timeout of "30" seconds with proposal responses "instantiateProposalResponses":
165+
And user "dev0Org0" sends proposal "instantiateProposal1" to endorsers with timeout of "90" seconds with proposal responses "instantiateProposalResponses":
166166
| Endorser |
167167
| peer0 |
168168
| peer2 |

0 commit comments

Comments
 (0)