Closed 1468ca0b-2a64-4fb4-8e52-ea5806644b4c closed 6 years ago
Created by: vvv
Can one of the admins verify this patch?
@chumakd Huh?
Created by: mero-ci
Can one of the admins verify this patch?
Created by: mero-ci
test
Created by: vvv
~👎 Halon unit tests fail.~
Quick way to reproduce: h0 test --fast mero-halon --ta '-p "smart test success"'
$ h0 test --fast mero-halon --ta '-p "smart test success"'
----- test --fast mero-halon --ta -p "smart test success" -----
mero-halon-0.2: test (suite: scheduler-tests, args: -p "smart test success")
All 0 tests passed (0.00s)
mero-halon-0.2: Test suite scheduler-tests passed
mero-halon-0.2: test (suite: tests, args: -p "smart test success")
mero-halon:tests
DriveFailure
Drive failure, successful reset and smart test success: FAIL
Exception: user error (failDrive: SSPL wasn't sent [ActuatorRequestMessageActuator_request_typeNode_controller {actuatorRequestMessageActuator_request_typeNode_controllerNode_request = "RESET_DRIVE: serial1_5"}])
1 out of 1 tests failed (26.54s)
mero-halon-0.2: Test suite tests failed
Test suite failure for package mero-halon-0.2
tests: exited with: ExitFailure 1
Logs printed to console
Created by: vvv
Created by: vvv
Change RabbitMQ bindings parameters (exchange name, routing key, queue name): make them identical to those used at SSPL side. Halon and SSPL won't be able to communicate if those parameters differ.