You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test(smoke): exercise medkit REST round-trip via arm-self-test, drop BT-motion dependency
The previous assertion ('MANYMOVE_PLANNER_* fault appears after
inject-collision') is brittle in CI: setting the BT blackboard
'collision_detected' flag only triggers a fault when
MoveManipulatorAction::onStart actually ticks. The CI fake-hardware launch
does not auto-issue motion goals, so the BT remains idle and the flag is
read by nothing.
Replace with:
- Loop over inject-collision + restore-normal endpoints to prove the
manifest <-> container_scripts component-id binding (the previous
manymove-planning 404 root cause).
- arm-self-test script execution + poll for MANYMOVE_SELFTEST fault: this
exercises the medkit REST -> FaultManager pipeline directly via
/fault_manager/report_fault, with no BT trajectory state dependency.
Real BT-emitted fault verification stays the responsibility of the
record_full.sh demo runs, which do start moves and observe the full
round-trip.
0 commit comments