mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-10 04:36:40 +00:00
kevinveenbirkenbachandClaude Opus 5
dc54e6d83f
Every one of these call sites ended in `|| true`, so a failure left no trace and the surrounding script reported a clean run. service_converged.sh needed the `|| true` for a reason that had nothing to do with the command: under `set -o pipefail`, `head -10` closes the pipe and awk dies of SIGPIPE, which pipefail then reports as the pipeline's status. That made a genuine `container service ps` failure indistinguishable from a normal truncation. Capping inside awk (`n++ < 10`) removes the SIGPIPE, so the command status can be tested on its own and a real failure now prints why. give_up and report_failed_tasks carried a byte-identical copy of that block, so the fix lifts it into one report_tasks helper rather than applying it twice. The swarm-clean scripts keep going after a failed step on purpose, since the host layer below them clears what survives. They now say what did not work before continuing, instead of continuing silently. 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. ✅