Skip to content

[INTEROP-06] MQTT ports' service-container interop pattern is the strongest in the ecosystem — recommend adopting it as the standard #151

Description

@SoundMatt

Finding. The MQTT ports (go-mqtt, rust-MQTT) reportedly run their external-interop tests against a
real eclipse-mosquitto service container plus the mosquitto_pub/mosquitto_sub reference CLIs
— materially stronger than the DDS/CAN family's probe-then-skip pattern (see INTEROP-05, filed
separately in this batch), because the broker is guaranteed present on every CI run; tests only skip
if the CLI tooling itself is absent, which is a narrower and more visible failure mode.

Recommendation. Migrate the DDS and CAN interop jobs from probe-then-skip to the same
service-container / guaranteed-image model the MQTT family already uses, eliminating the silent-skip
failure mode identified in INTEROP-05 at the same time.


Filed from the 2026-07-29 ecosystem audit register; independently re-verified against current HEAD before filing.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions