docs(smoke): capture-logs scripts + runbook sync (beta.52 + Module 15)#325
Merged
Conversation
- New capture-logs.sh / capture-logs.ps1: one-shot diagnostic snapshots (AVC, service journal/status, fcontext, SELinux labels, processes, dataRoot / Program Files / temp listings, config, app logs) to a timestamped labeled folder + archive - run at any checkpoint, esp. on failure. The Windows one captures the wipe leftover + the temp cleaner copy (the in-app uninstall cleaner is --no-log by design). - Wired references into all three docs (pre-flight + stop-rules + the 15.2 wipe row). - smoke-runbook.md: bump smoke-target tag beta.50 -> beta.52 (missed in the earlier sync), add the missing Module 15 (Windows uninstall + stop-exit), fix the stale "69 tests" count -> 74. - smoke-full.md: mark the wipe-self-deletion VM concern fixed in beta.52.
bilbospocketses
added
the
release:none
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Smoke-test review follow-ups: log-capture tooling + a doc sync. No app code;
release:none.New - capture scripts
docs/smoke-tests/capture-logs.sh(Linux) andcapture-logs.ps1(Windows). Run... <test-id>at any checkpoint - especially the instant a test fails - to snapshot a complete evidence bundle (AVC denials, service journal+status, SELinux fcontext + labels, processes, dataRoot / Program Files / temp listings, config.json, app logs) into a timestamped, labeled folder + an archive to attach. Numbered output files map to each row's verify step.control\operation-server\) and the temp cleaner copy, since the in-app uninstall cleaner is--no-logby design - so the filesystem/registry/temp state is the only evidence.Runbook sync (it had drifted)
beta.50->beta.52(missed when checklist + full were bumped).full
Why
The smoke is the 0.1.30 gate and runs on VMs that can't be introspected remotely - a one-command evidence capture makes every failure diagnosable from the attached bundle instead of "it didn't work."