Closed litong01 closed 3 years ago
There has been a significant reworking of the caliper internals within the 0.4.0 release, so it is possible that this is now fixed in those changes
This was due to trying to invoke the caliper cli as follows
docker run --network mynetwork --name calipertester --hostname calipertester --rm
-e "ROOTPATH=/vars/keyfiles"
-v /var/run/docker.sock:/var/run/docker.sock
-v $(pwd)/vars:/vars
hyperledger/caliper:0.3.2
"launch master --caliper-benchconfig /vars/run/caliperbenchmarkconfig.yaml
--caliper-networkconfig /vars/run/calipernetworkconfig.json
--caliper-flow-only-test --caliper-fabric-gateway-usegateway --caliper-fabric-gateway-discovery"
The solution is to remove the quotes around the launch master
command
@davidkel that is not the cause of the issue. The command has been changed to this, but same issue.
docker run --network {{ NETNAME }} --name calipertester --hostname calipertester --rm
--entrypoint /hyperledger/caliper/workspace/run/caliperrun.sh
-e "ROOTPATH=/hyperledger/caliper/workspace/keyfiles"
-e "CALIPER-BENCHCONFIG=run/caliperbenchmarkconfig.yaml"
-e "CALIPER-NETWORKCONFIG=run/calipernetworkconfig.json"
-v /var/run/docker.sock:/var/run/docker.sock
-v {{ hostroot }}/vars:/hyperledger/caliper/workspace
hyperledger/caliper:0.3.2
You can see that it no longer uses the that.
The caliperrun.sh looks like this.
#!/bin/sh
rm -rf /hyperledger/caliper/workspace/caliper.log
caliper launch master \
--caliper-flow-only-test --caliper-fabric-gateway-usegateway --caliper-fabric-gateway-discovery \
--caliper-fabric-gateway-gatewaylocalhost false
@nklincoln @davidkel since 0.4.0 is out, let me give it a try anyway and see what happens.
after launch master using caliper container 0.3.2, caliper will hang
Context
Setup fabric network, network config and benchmark config file to launch caliper master to run the test, caliper launch master will hang
Expected Behavior
caliper launch master should return after txs all finish
Actual Behavior
the process hang after some txs finished successfully
Possible Fix
Steps to Reproduce
Existing issues
network config.json
benchmark config yaml file
This is using fabric 2.1.0 sdk.
Context
This basically blocks any process invokes the test.
Your Environment