search

hyperledger-archives / fabric

THIS IS A READ-ONLY historic repository. Current development is at https://gerrit.hyperledger.org/r/#/admin/projects/fabric . pull requests not accepted
https://gerrit.hyperledger.org/
Apache License 2.0
1.17k stars 1.01k forks source link

more behave tests failure with latest hyperledger code #1080

Closed gongsu832 closed 8 years ago

gongsu832 commented 8 years ago

commit 8580de69c9371e26342068746e6340169711a5dc

Failing scenarios:
  peer_basic.feature:420  chaincode example02 with 4 peers and 1 membersrvc, issue #567 -- @1.1 Consensus Options
  peer_basic.feature:421  chaincode example02 with 4 peers and 1 membersrvc, issue #567 -- @1.2 Consensus Options
  peer_basic.feature:422  chaincode example02 with 4 peers and 1 membersrvc, issue #567 -- @1.3 Consensus Options
  peer_basic.feature:423  chaincode example02 with 4 peers and 1 membersrvc, issue #567 -- @1.4 Consensus Options
  peer_basic.feature:504  chaincode example02 with 4 peers and 1 membersrvc, issue #680 (State transfer) -- @1.1 Consensus Options
  peer_basic.feature:505  chaincode example02 with 4 peers and 1 membersrvc, issue #680 (State transfer) -- @1.2 Consensus Options
  peer_basic.feature:506  chaincode example02 with 4 peers and 1 membersrvc, issue #680 (State transfer) -- @1.3 Consensus Options
  peer_basic.feature:555  chaincode example02 with 4 peers and 1 membersrvc, issue #724 -- @1.1 Consensus Options
  peer_basic.feature:633  4 peers and 1 membersrvc, consensus still works if one backup replica fails -- @1.1 Consensus Options
  peer_basic.feature:634  4 peers and 1 membersrvc, consensus still works if one backup replica fails -- @1.2 Consensus Options
  peer_basic.feature:635  4 peers and 1 membersrvc, consensus still works if one backup replica fails -- @1.3 Consensus Options
  peer_basic.feature:695  4 peers and 1 membersrvc, consensus fails if 2 backup replicas fail -- @1.1 Consensus Options
  peer_basic.feature:696  4 peers and 1 membersrvc, consensus fails if 2 backup replicas fail -- @1.2 Consensus Options
  peer_basic.feature:697  4 peers and 1 membersrvc, consensus fails if 2 backup replicas fail -- @1.3 Consensus Options
  peer_basic.feature:740  4 peers and 1 membersrvc, consensus still works if 1 peer (vp3) is byzantine -- @1.1 Consensus Options
  peer_basic.feature:741  4 peers and 1 membersrvc, consensus still works if 1 peer (vp3) is byzantine -- @1.2 Consensus Options
  peer_basic.feature:742  4 peers and 1 membersrvc, consensus still works if 1 peer (vp3) is byzantine -- @1.3 Consensus Options

0 features passed, 1 failed, 0 skipped
6 scenarios passed, 17 failed, 2 skipped
242 steps passed, 17 failed, 264 skipped, 0 undefined
Took 17m10.412s

Are these expected? Before moving to hyperledger code, I typically get 2-4 failures with the older openblockchain code. Full log attached in case you want to look at it.

behave.log.zip

bcbrock commented 8 years ago

@gongsu832 I see that at least some of these are timeouts. I see them as well. Please try changing the timeout on line 399 of fabric/bddtests/steps/peer_basic_impl.py from 3 to 30 and try again. When I did this all but 3 fails went away for me.

gongsu832 commented 8 years ago

@bcbrock thanks a lot. With that change I now only have 1 fail on one of the machines. The rest pass all the tests.