Files
cc-ci/tests/mumble/test_backup.py
autonomic-bot 9a7772563a style: repo-wide lint pass — make the lint gate green again
Push builds have been RED on the lint step since ~build 209 from accumulated
formatting drift. This is the mechanical cleanup: ruff format + ruff --fix
(UP038 isinstance unions, SIM105 contextlib.suppress, UP031 f-strings, SIM115
tempfile context manager), shfmt -i 2 -ci, nixpkgs-fmt/statix/deadnix (merged
attrsets, dropped unused lib args), yamllint, and shell quoting fixes in
tests/lasuite-docs/setup_custom_tests.sh. No behaviour changes intended;
lint: PASS, unit tests: 138 passed.
2026-06-09 21:56:15 +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"