wolk-jjba-1ec6f966-ed14

job failed

starting new job...


→ running command: dir='/etc/byggsteg/job-clone//wolk-jjba/trunk'
branch='trunk'
if ! command -v git >/dev/null 2>&1; then
  echo 'byggsteg: git is not on this deployment PATH, so the clone cannot be updated' >&2
  exit 1
fi
if ! cd "$dir"; then
  echo "byggsteg: cannot enter the clone $dir" >&2
  exit 1
fi
root=$(git rev-parse --show-toplevel 2>/dev/null)
if [ "$root" != "$(pwd -P)" ]; then
  echo "byggsteg: $dir is not a git checkout; remove it and the next run clones it again" >&2
  exit 1
fi
if ! origin=$(git remote get-url origin 2>/dev/null); then
  echo "byggsteg: $dir has no origin remote to fetch $branch from" >&2
  exit 1
fi
before=$(git rev-parse --short HEAD 2>/dev/null) || before=none
attempt=1
while :; do
  if GIT_TERMINAL_PROMPT=0 git fetch --quiet origin "+refs/heads/$branch:refs/remotes/origin/$branch"; then
    break
  fi
  if [ "$attempt" -ge 3 ]; then
    echo "byggsteg: could not fetch $branch from $origin after 3 attempts; is the branch still there, and is the remote reachable?" >&2
    exit 1
  fi
  echo "byggsteg: fetching $branch from $origin failed; retrying in $((attempt * 2))s" >&2
  sleep $((attempt * 2))
  attempt=$((attempt + 1))
done
if ! git checkout --quiet --force -B "$branch" FETCH_HEAD; then
  echo "byggsteg: fetched $branch from $origin but could not check it out" >&2
  exit 1
fi
after=$(git rev-parse --short HEAD)
if [ "$before" = "$after" ]; then
  echo "byggsteg: $branch was already at $after"
else
  echo "byggsteg: $branch moved from $before to $after"
fi


byggsteg: trunk was already at 4655f5c

→ running command: cd /etc/byggsteg/job-clone/wolk-jjba/trunk && uname -a

Linux wolk-jjba 7.2.11-gnu #1 SMP PREEMPT_DYNAMIC 1 x86_64 GNU/Linux

→ running command: cd /etc/byggsteg/job-clone/wolk-jjba/trunk && git log --name-status HEAD^..HEAD

commit 4655f5c2d69aee30fb833e194e12c995fe5b82f1
Author: Josep Bigorra <jjbigorra@gmail.com>
Date:   Thu Oct 29 22:03:22 2026 +0100

    feat: Improve container setup

M       README.org
M       src/wolk-jjba/containers.scm
M       test/veritas/unit/containers-spec.scm

→ running command: cd /etc/byggsteg/job-clone/wolk-jjba/trunk && maak test

channels.scm:35:6: warning: channel 'jointhefreeworld' is not trusted
Updating channel 'guix' from Git repository at 'https://codeberg.org/guix/guix.git'...
Updating channel 'jointhefreeworld' from Git repository at 'https://codeberg.org/jjba23/guix-jointhefreeworld'...
Authenticating channel 'jointhefreeworld', commits b0ac3f0 to 913fb4b (2 new commits)...
▕███████████████████████████████████████                                       ▏guix time-machine: error: commit 913fb4b872c397f5bc97744dad6a81a790ed1ad7 lacks a signature


--------------------------------------------------------------

Maak 0.14.0: the infinitely extensible command runner

Loading tasks from Maak file: /etc/byggsteg/job-clone/wolk-jjba/trunk/maak.scm

Executing Maak tasks: test


--------------------------------------------------------------

=> Running Maak task: test

  Run the Veritas unit-test suite, one process per test file.

Runs inside the manifest shell like the other Scheme tasks: the suite
imports (guix gexp) and (gnu services ...) and needs veritas, none of
which are in the machine's system profile, so a bare `guile' fails with
`no code for module (veritas runner)' -- which is what the Byggsteg CI
task `maak-test' used to hit.

The files run in parallel, one process each, in as many processes as
this machine may use up to four; VERITAS_JOBS overrides that count.
Four things are deliberate, so that a failure here is a failure of the
code under test rather than of the schedule:

  - the order the files run in is shuffled, and the seed is printed:
    `VERITAS_SEED=<the seed> VERITAS_SHUFFLE_FILES=true maak test'
    replays a failing order, and `VERITAS_SHUFFLE_FILES=false' runs them
    in the fixed one;
  - every fixture is created under a name unique to the run and removed
    when it ends (see test/veritas/temp.scm), so two workers -- or two CI
    jobs sharing /tmp -- cannot collide on one;
  - GUILE_LOAD_PATH names the channel's module directory, because
    evaluating config.scm needs the jointhefreeworld channel and the pinned
    shell does not carry it -- worked out from the pulled guix when there is
    one and from the guix that pinned the channels when there is not (see
    the comments above);
  - a suite that needs the network or the machine's own root-only files
    is a suite that fails for reasons nobody can act on, and there is
    none of those: see the Commentary of each spec.

Executing: env VERITAS_JOBS=1 guix time-machine --channels=channels.scm -- shell -m manifest.scm -- env GUILE_AUTO_COMPILE=0 XDG_CACHE_HOME=/tmp/wolk-jjba-test-20775-cache guile -L ./src -L ./test -c '(use-modules (veritas runner)) (run-tests)'

maak: error: command failed (exit code 1): env VERITAS_JOBS=1 guix time-machine --channels=channels.scm -- shell -m manifest.scm -- env GUILE_AUTO_COMPILE=0 XDG_CACHE_HOME=/tmp/wolk-jjba-test-20775-cache guile -L ./src -L ./test -c '(use-modules (veritas runner)) (run-tests)'
        hint: Fix the command above, or run `maak --dry-run' to inspect it first.
inspect the job's lambda expression
(lambda()
  `((task . ("maak-test"))
    (project . "wolk-jjba")
    (branch-name . "trunk")
    (clone-url . "https://github.com/jjba23/wolk-jjba.git")))