Files
computer-playbook/scripts/tests
kevinveenbirkenbachandClaude Opus 5.5 283cdd86bd fix(ci): keep the inventory artifact and the first error on a budget kill
A compose job that runs out of its distro budget is stopped by
`timeout -k 60` in distros.sh: SIGTERM at the deadline, SIGKILL 60 s
later. dedicated.sh's cleanup trap copied the generated inventory out of
the DinD container only after the rescue capture, which alone took 266 s
in Baserow#0 (run 40625679270), so the kill always landed first. The zip
step then failed with "No inventory found", never wrote INVENTORY_ZIP,
and the upload step failed again on an empty `path`; two follow-up errors
buried the real `rc=137`. Nextcloud#0 and #2 of the same run show the
same trio.

- The inventory copy moves unchanged to the top of the trap, ahead of
  the Playwright copy and the rescue capture; the three write to
  disjoint directories and none reads another's output.
- The zip step writes INVENTORY_ZIP before running the zip script, so a
  missing zip falls under the upload's existing
  `if-no-files-found: ignore` instead of failing the step a second time.

The budget overrun itself came from the docs README replay pulled into
the round through partners, which 91022ad37a removes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-28 17:13:51 +01: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. ✅