mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 03:38:23 +00:00
kevinveenbirkenbachandClaude Opus 5
5f6dedf7a8
The job could sit silent for its full 30-minute budget and only then print five groups, so a hanging distro was indistinguishable from a slow one. Each container's output is stamped with [distro][HH:MM:SS] as it arrives, and the per-distro verdict is printed when that distro finishes rather than at the end. A pipeline hands $! the pid of tee rather than of the test, which would have turned every DNS failure into a green job, so each run goes through a subshell under pipefail. The ::error:: annotation, the per-distro logs and the container cleanup are unchanged. 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. ✅