Files
iceman1001andClaude Opus 5 3a2b173319 docker/build-all.sh: report which images failed
The loop threw away each subshell's status and had no set -e, so a failed
docker build left no trace but docker's own error text, buried in the
scrollback of 17 image builds. Worse, a for loop exits with the status of its
last iteration, so the script returned 0 whenever the final entry succeeded,
no matter how many earlier ones had failed.

Collect the failures and print them as a summary, exit 1 if there are any.
A name in the list with no matching directory is counted as a failure too
rather than passing by as a one-line cd error, which is how ubuntu-24.10 has
been quietly skipped since that directory went away.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-11-14 10:54:14 +07:00
..
2026-04-14 10:15:46 +02:00
2026-09-17 22:48:34 +02:00
2026-09-17 22:48:34 +02:00
2026-04-14 10:15:46 +02:00
2026-04-14 10:15:46 +02:00
2026-04-14 10:15:46 +02:00
2026-04-14 10:15:46 +02:00
2026-04-14 10:15:46 +02:00
2026-04-14 10:15:46 +02:00
2026-04-14 10:15:46 +02:00
2026-04-14 10:15:46 +02:00
2026-02-26 20:37:45 +01:00
2026-09-17 22:48:34 +02:00
2026-02-26 20:37:45 +01:00
2026-09-17 22:48:34 +02:00
2026-02-21 15:02:48 +01:00

Docker tests

Usage:

  • enter one of the subfolders
  • ../build.sh to build the docker image
  • ../run.sh to run a container and get a shell
  • ../run.sh tests to run a container and execute its run_tests.sh