Files
computer-playbook/scripts/tests
kevinveenbirkenbachandClaude Opus 4.8 e5fd4b11d0 fix(test/swarm): NFS state-path, image pull retry, multi-service converge gate
Swarm deploy-test harness fixes (run 28439744622); swarm-test-harness only,
compose path untouched:

- NFS_STATE_PATH (<export>/infinito-state/<vol>): per-volume dirs are nested
  under the fsid=0 state subdir (STORAGE_NFS_STATE_SUBDIR), but the seed,
  assert and diagnostics used the bare export base -> "Directory nonexistent".
  00_topology derives it, the workflow exports it, 09/11/12 consume it.
- pull-retry: pre-pull jrei/systemd-ubuntu with bounded retries before
  docker run, so a Docker Hub registry blip no longer fails the job (exit 125).
- jitsi: derive the converge/drain SERVICE_NAME from proxy.service_key so
  multi-service stacks (jitsi_jitsi-web/-jvb/...) resolve; single-service apps
  fall back to the entity name (unchanged).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 22:51:50 +02:00
..

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. ✅