Mark S. Lewis 92cb79d9db Fix build with new microfab release ... The new microfab release seems to start slower than the previous release. This might be due to a change from solo to raft consensus. This causes failures in the full-stack-asset-transfer appdev tests. Chaincode deployment fails since the channel is not yet available. Instead of increasing the sleep time after launching microfab, this change attempts to wait however long is required by looking for the "Microfab started" message in the container log before proceeding. The test script is also updated to correctly stop the external chaincode process when the script exits. Previously the process ID of the npm command used to lauch the chaincode was captured rather than the actual chaincode process. Signed-off-by: Mark S. Lewis <Mark.S.Lewis@outlook.com>		2024-11-28 01:20:53 +00:00
..
00-chaincode-e2e.sh	Moves the Full Stack Asset Transfer Development Guide to fabric-samples (#852)	2022-11-10 10:40:27 -05:00
10-appdev-e2e.sh	Fix build with new microfab release	2024-11-28 01:20:53 +00:00
20-cloud-e2e.sh	Run FSAT tests with 2.5 images, binaries, and trigger on all builds for regression coverage (#919)	2023-01-27 09:49:52 -05:00
30-ansible-e2e.sh	Moves the Full Stack Asset Transfer Development Guide to fabric-samples (#852)	2022-11-10 10:40:27 -05:00
40-console.sh	Moves the Full Stack Asset Transfer Development Guide to fabric-samples (#852)	2022-11-10 10:40:27 -05:00