+31
−8
Loading
Two things that make the suite unusable in a container, both fixable without
touching a single test.
logUtils' `Output` keyword documents a `console` argument - "If false, the JSON is
not written to terminal" - and ignored it, passing also_console=True on every
line. A full run is ~4400 request/response pairs, so the terminal receives about
175,000 lines and the one line per test that says what happened is lost in it. The
argument is honoured now, and ETSI_QUIET_IO=1 switches the echo off globally
without editing tests. Nothing is lost: logger.info still writes to log.html,
which is where a failure gets investigated.
Start Mqtt Server ran `docker run eclipse-mosquitto`, which cannot work where
there is no docker daemon - a CI job that is itself a container, for one. All
twelve 058_* tests then failed at setup with "Connection refused", which reads as
a broker fault and is not one. Where docker is absent but mosquitto is present, it
now starts the daemon directly with the same configuration: the listener port and
the password-file path are rewritten out of the container's paths, and the
password file is made readable because mosquitto drops privileges when started as
root and cannot otherwise read a root-owned file. Stop does whichever matches.
Both are candidates for upstream: the first is a documented argument that did not
work, the second is portability with no behaviour change where docker exists.
Co-Authored-By:
Claude Opus 5 (1M context) <noreply@anthropic.com>