Files
cc-ci/tests/mumble/test_backup.py
T
notplantsandClaude Fable 5.1 9a80002b37
continuous-integration/drone/push Build is failing
lint: ruff format + one auto-fix so the push self-test is green again
`scripts/lint.sh --fix` from the pinned lint devshell: 90 Python files
reformatted (ruff format, mechanical) and one C420 (dict comprehension →
dict.fromkeys) in tests/unit/test_f211_sso_skip.py. The push self-test had
been failing at the lint stage since build 1313 (2026-08-31) on exactly
these files; nothing else changed.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FqkQq3CDmFWcQ7u1LzoyRz
2026-09-07 21:15:05 +00:00

29 lines
1.2 KiB
Python

"""mumble — BACKUP overlay (Phase 1e HC3 / Phase 2 P4): assertion-only + additive.
ops.pre_backup seeded ci_marker='original' into /data/mumble-server.sqlite before the backup op
(the recipe's backupbot pre-hook `.backup`s that exact file). The orchestrator performed the backup
once (generic tier asserted a snapshot artifact). This overlay ADDS: the seeded row is intact at
backup time. The backup→restore divergence (dropping the table) is in ops.pre_restore.
"""
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):
# Set the busy timeout via the SILENT `.timeout` dot-command (-cmd), NOT an inline
# `PRAGMA busy_timeout=...` (which emits its own result row and would pollute read-backs).
cmd = f'sqlite3 -cmd ".timeout 20000" {DB} "{sql}"'
return lifecycle.exec_in_app(domain, ["sh", "-c", cmd], service="app").strip()
def test_backup_captures_state(live_app):
assert _sqlite(live_app, "SELECT v FROM ci_marker;") == "original", (
"the seeded mumble sqlite marker was not present at backup time"
)