mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 12:17:13 +00:00
kevinveenbirkenbachandClaude Opus 4.7
e0ef4dcc98
probe_did_inner_build() in scripts/tests/environment/utils/cache.sh hardcoded the compose network as `infinito-nexus_default`. Compose derives the network name from the project name, which defaults to the host CWD basename — `infinito-nexus` locally, `infinito-nexus-core` in the CI fork, something else again in Act runners and worktrees. CI therefore failed the test-environment matrix on every distro with `network infinito-nexus_default not found` even though the cache stack itself was healthy. Look up the network the running `infinito-package-cache-frontend` container is actually attached to via `docker inspect` and use that. Fail loudly if discovery returns empty rather than silently skipping the probe. Verified via `make act-workflow ACT_WORKFLOW=.github/workflows/test-environment.yml ACT_JOB=test-environment ACT_MATRIX='dev_runtime_image:debian:bookworm'` — Job succeeded, probe step reports `[OK] DiD inner-build flowed through cache frontend`. Co-Authored-By: Claude Opus 4.7 (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. ✅