mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-10 12:47:04 +00:00
kevinveenbirkenbachandClaude Opus 5
d0937b0bb7
Three places where a data-root verdict was produced and then lost. report.sh matched `requested=[a-z]+`, which never matches `ext4`. Against the real deploy log of a run that recorded five ext4 verdicts, the old pattern yields 0 matches and the summary table was silently empty of them; the fixed pattern aggregates the same five into one row. docker_dataroot.sh wrote the reason only to GITHUB_STEP_SUMMARY, which is unset inside the lab node containers - so on exactly the machines that decline, the reason went nowhere. It now rides on the machine-readable report line too. This is what leaves the mariadb drill's decline reason unrecoverable from run 30781723102. resolve.sh's exclusions went to stderr only, i.e. into the deploy log rather than the job summary. The reason is emitted as a list below the table, not as a column: reasons embed per-node data (the pool name carries the hostname, plus the loop device), so folding them into the `sort | uniq -c` key would split one five-node row into five one-node rows exactly in the failure case the reason exists to explain. `reason=[^']*` keeps ansible's closing quote out of the value, and `|` is replaced so a reason cannot break the markdown table. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Test Utilities 🧪
This directory holds the operational side of testing in Infinito.Nexus.
These assets are meant to support confidence, not ceremony. They help the project validate real-world behavior across local development, CI environments, and deployment-oriented smoke tests. The emphasis is on practical feedback: when something breaks, the surrounding test tooling should make the failure easier to understand, easier to reproduce, and easier to clean up. 🚀
Good changes in this area usually make the test experience more:
- repeatable
- diagnosable
- environment-aware
- safe to rerun
The ideal outcome is boring reliability: contributors should be able to trust that a test run says something meaningful about the system, not just about the machine that happened to execute it. ✅