mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-09-11 14:00:29 +00:00
rcourtman
a64dd2f005
Mock mode never exercised the backup-running states from "Stop showing an in-flight backup as a completed one": no guest carried BackupInProgress, no PBS listing showed an in-flight snapshot, and no vzdump task was ever running, so the blue Running badge and the Running artifact chips had no local reproduction. A post-scenario fixture now flags roughly one guest in twenty-five per last-backup age bucket - never, fresh, stale, overdue - so the Running badge appears alongside every badge story, and gives each flagged guest the evidence a live run actually produces: an in-flight PBS snapshot shaped the way the PBS API lists one still being written (no size, no verification, only the guest config blob in files) and a running vzdump task with no end time. Running after applyDemoBackupScenario keeps the per-tick reapplication idempotent, because the scenario's curated sweep drops the previous pass's artifacts before the fixture re-adds them. The first-cycle showcase guests are excluded: their exact rows are pinned by the demo posture tests (a failed run three hours ago, a guest with no recovery evidence at all), and a backup running right now would mask exactly the states those rows exist to demonstrate. Later profile cycles repeat the same stories under suffixed names, so the fixture draws its running guests from them.