Johnathan Corgan 217bea3086 Show why a deb-install image build or container start failed ...

The deb-install suite sent the output of its runtime image build and of
its container start to /dev/null, so a registry timeout or a container
that was never created surfaced only as "runtime build failed" with the
cause thrown away. The dns-resolver suite already captured that output
and printed it on failure.

Move its capture helpers into testing/lib/image-build.sh and use them in
both suites, so a failed build or start in deb-install prints what docker
said. The dns-resolver change is a move only. Also correct the
deb-install header, which still described the package build it no longer
does itself.

2026-09-19 13:30:33 +00:00

..

__init__.py

Consolidate Docker test harness infrastructure

2026-03-19 18:08:36 +00:00

derive_keys.py

Pin the chaos mesh root to n01 so scenario diagrams describe the real tree

2026-07-23 15:43:10 +00:00

image-build.sh

Show why a deb-install image build or container start failed

2026-09-19 13:30:33 +00:00

log_analysis.py

Stop the log analyzer double-counting outbound peer promotions

2026-07-26 14:24:44 +00:00

relay-verdict.sh

test(nat): contain strfry relay aborts in the NAT lab

2026-09-19 09:11:46 +00:00

systemd-container.sh

fix(testing): boot the systemd install containers without --privileged

2026-09-11 02:51:45 +00:00

wait-converge-test.sh

test: let the rekey convergence gate hand a near-converged mesh to the strict assertion

2026-09-19 03:25:45 +00:00

wait-converge.sh

test: let the rekey convergence gate hand a near-converged mesh to the strict assertion

2026-09-19 03:25:45 +00:00