MQTT Failures in Integration Tests

[shemnon]

Running the Sawtooth and Ethereum/Besu integration tests always fails since 0.3.0 complaining about mqtt failures.

Context

The integration tests fail to run because of reasons unrelated to the systems under test.

Expected Behavior

I expect the integration tests to execute sucessfuly, or fail for reasons specific to the system under test.

Actual Behavior

Caliper is unable to stand up the Systems under test because of MQTT messages relating to the "prepared" state

Steps to Reproduce

1. run the integration tests for Ethereum, Besu, or Sawtooth
2. Observe in the log messages such as

2020.03.19-10:02:18.088 -0600 debug [mqtt-worker-messenger] ethereum worker sent message: {"to":["orchestrator"],"from":"41953","timestamp":"2020-03-19T16:02:18.088Z","data":{"error":"SyntaxError: Invalid or unexpected token","type":"prepared"}}
2020.03.19-10:02:18.089 -0600 debug [process-master-messenger] Processing worker message: {"to":["orchestrator"],"from":"41953","timestamp":"2020-03-19T16:02:18.088Z","data":{"error":"SyntaxError: Invalid or unexpected token","type":"prepared"}}
2020.03.19-10:02:18.110 -0600 debug [worker-orchestrator] Dealing with prepared message {"to":["orchestrator"],"from":"41953","timestamp":"2020-03-19T16:02:18.088Z","data":{"error":"SyntaxError: Invalid or unexpected token","type":"prepared"}}
2020.03.19-10:02:18.110 -0600 error [message-handler] Handled unsuccessful "prepare" message for worker 0 and test round 0 with error SyntaxError: Invalid or unexpected token
2020.03.19-10:02:18.110 -0600 debug [worker-orchestrator] Handling prepared message from 41953 with data {"error":"SyntaxError: Invalid or unexpected token","type":"prepared"}

Context

I am unable to evolve the Ethereum adapter to fix other bugs (such as nonce management)

Your Environment

• Version used: Caliper 0.3.0, bffcd48
• Environment name and version (e.g. Chrome 39, node.js 5.4): Node v10.16.3
• Operating System and version (desktop or mobile): Mac OSX 10.15.3
• Link to your project:

[aklenik]

@shemnon I think this was fixed by #782. Can you confirm it?

[shemnon]

Yea, besu works now.