mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 19:01:54 +00:00
kevinveenbirkenbachandClaude Opus 5
a8a8396fa3
The data-root task runs on all five swarm nodes at once, and they are containers on one host kernel sharing its loop devices. losetup -f only names the next free one; by the time the following losetup attached it, a sibling had taken it - 'failed to set up loop device: Device or resource busy'. Claim with --find --show, which picks and attaches in one call, and retry with a short pause when a sibling wins anyway. The step runs before anything is pulled, so on some nodes docker is not installed yet and the closing 'systemctl start docker' died with rc=5, taking the whole task with it under set -e. The two systemctl stop calls above it had tolerated that all along. Start only when the unit exists, and report applied-pending-docker instead of applied so the job summary stops claiming a data root that no daemon has picked up yet. 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. ✅