Files
cc-ci/tests/mumble/ops.py
autonomic-bot 6841048aae feat(2): Q4.2 mumble — parity port (health/protocol-handshake/web) + 2 specific + P4 sqlite
- functional/_mumble_proto.py: stdlib Mumble TLS protocol client (adapted from corpus mumble_connect.py)
- 3 parity ports: test_tcp_health, test_protocol_handshake (channel presence+ServerSync), test_web_client
- 2 NEW recipe-specific (P3): welcome-text + max-users config round-trips over the protocol
- P4: ops.py + test_backup/test_restore seed ci_marker in /data/mumble-server.sqlite (recipe's own backupbot DB), busy_timeout for live-server locks
- test_install overlay: voice server listening on 64738 (beyond web-sidecar readiness)
- recipe_meta: COMPOSE_FILE=compose.yml:mumbleweb:host-ports; WELCOME_TEXT/USERS markers
- PARITY.md mapping table

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-05-29 19:20:56 +01:00

52 lines
2.0 KiB
Python

"""mumble — pre-op seed hooks (Phase 1e HC3 / Phase 2 P4 backup data-integrity).
The orchestrator runs these BEFORE each op; the matching test_<op>.py asserts post-op (assertion
only). mumble persists its server state (registered users/channels/ACLs/config) in the sqlite DB
`/data/mumble-server.sqlite`, and the recipe's backupbot hooks dump/restore exactly that file
(`sqlite3 ... ".backup backup.sqlite"` pre-hook; `mv backup.sqlite mumble-server.sqlite` restore
post-hook). So real backup data-integrity = seed a marker row into that sqlite, back up, mutate,
restore, and prove the seeded row survived — the same DB the recipe actually backs up.
The murmur server holds the DB open, so all writes use `PRAGMA busy_timeout` to wait out the
server's transient locks rather than failing with "database is locked". The marker lives in a
dedicated `ci_marker` table murmur never touches.
"""
import os
import sys
sys.path.insert(0, os.path.join(os.path.dirname(__file__), "..", "..", "runner"))
from harness import lifecycle # noqa: E402
DB = "/data/mumble-server.sqlite"
def _sqlite(domain, sql):
cmd = f'sqlite3 {DB} "PRAGMA busy_timeout=20000; {sql}"'
return lifecycle.exec_in_app(domain, ["sh", "-c", cmd], service="app").strip()
def _seed(domain, value):
_sqlite(
domain,
"CREATE TABLE IF NOT EXISTS ci_marker(v TEXT); DELETE FROM ci_marker; "
f"INSERT INTO ci_marker VALUES('{value}');",
)
got = _sqlite(domain, "SELECT v FROM ci_marker;")
assert got == value, f"seed did not commit (read back {got!r}, expected {value!r})"
def pre_upgrade(domain, meta):
_seed(domain, "upgrade-survives")
def pre_backup(domain, meta):
_seed(domain, "original")
def pre_restore(domain, meta):
# diverge from the backup so a successful restore is observable: drop the marker table.
_sqlite(domain, "DROP TABLE IF EXISTS ci_marker;")
got = _sqlite(domain, "SELECT name FROM sqlite_master WHERE type='table' AND name='ci_marker';")
assert got == "", f"drop did not take (sqlite_master still lists ci_marker: {got!r})"