lambdock-ef704e39-2213

job failed

starting new job...
rundir='/etc/byggsteg/job-clone//lambdock/trunk succeeded43 lines · 0.7s
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 moved from 76a1771 to cc60691
setupuname -a succeeded1 lines · 0.0s
Linux wolk-jjba 7.2.11-gnu #1 SMP PREEMPT_DYNAMIC 1 x86_64 GNU/Linux
setupgit log --name-status HEAD^..HEAD succeeded23 lines · 0.0s
commit cc606915199184be24240b39c0ba0d81b09b1fe1
Author: Josep Bigorra <jjbigorra@gmail.com>
Date:   Mon Nov 16 17:36:33 2026 +0100

    release: v2.0.1, and every recipe builds with make
    
    The last meson references go: `maak.scm`'s build and test tasks run `make build`
    and `make check` (which is the Rust suite, the lints and the 342 Scheme
    assertions), the test job no longer wraps the run in Xvfb because the suite needs
    no display, and the package lists name cargo and the generators rather than meson
    and ninja.  The Dockerfile, the Debian rules, the openSUSE spec, the Arch
    PKGBUILD and the Flatpak manifest were already pointed at `make` in the release
    before this one.
    
    `tests/run_scheme_tests.sh` and `tests/scheme` are in the tree again, so the
    `make check` step that runs them exists.
    
    Suite: cargo 312 passed, clippy clean, `make check` green end to end (342 Scheme
    assertions included), and the release binary still builds the dock's 25 items
    from the real settings file with no criticals.

M       NEWS.org
M       maak.scm
M       rust/Cargo.lock
M       rust/Cargo.toml
testmaak test failed36 lines · 2.3s
     Removed 0 files
cargo test --offline --locked --manifest-path rust/Cargo.toml
error: failed to calculate checksum of: /etc/byggsteg/job-clone/lambdock/trunk/rust/vendor/system-deps/src/tests/test.tar.xz

Caused by:
  failed to open file `/etc/byggsteg/job-clone/lambdock/trunk/rust/vendor/system-deps/src/tests/test.tar.xz`

Caused by:
  No such file or directory (os error 2)
make: *** [Makefile:44: test] Error 101
;;; note: source file /etc/byggsteg/job-clone/lambdock/trunk/maak.scm
;;;       newer than compiled /root/.cache/guile/ccache/3.0-LE-8-4.6/etc/byggsteg/job-clone/lambdock/trunk/maak.scm.go
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;;       or pass the --no-auto-compile argument to disable.
;;; compiling /etc/byggsteg/job-clone/lambdock/trunk/maak.scm
;;; compiled /root/.cache/guile/ccache/3.0-LE-8-4.6/etc/byggsteg/job-clone/lambdock/trunk/maak.scm.go

maak: error: command failed (exit code 2): guix time-machine --channels=channels.scm -- shell -m manifest.scm -- /bin/sh -c 'set -eu; cargo clean --manifest-path rust/Cargo.toml; make check'
        hint: Fix the command above, or run `maak --dry-run' to inspect it first.


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

Maak 0.14.0: the infinitely extensible command runner

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

Executing Maak tasks: test


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

=> Running Maak task: test

  Build and run the whole test suite headlessly.

The shell wrapper only applies to the first command, so the pipeline is run by
one inner `sh -c' instead of a bare `&&': otherwise `cargo' would execute
outside the Guix environment.

The suite needs no display: every test is a decision, so it runs where the
manifest shell does, with `make check' -- which is the suite, the lints and the
Scheme tests in one target.

The cargo target directory is thrown away first: the Byggsteg job clone survives
between jobs, and a tree built by a different toolchain can leave artifacts that
no longer match the checked out sources. Rebuilding from scratch also means the
passing tests are the ones that match this commit.

  Execute command:
guix time-machine --channels=channels.scm -- shell -m manifest.scm -- /bin/sh -c 'set -eu; cargo clean --manifest-path rust/Cargo.toml; make check'

Executing: guix time-machine --channels=channels.scm -- shell -m manifest.scm -- /bin/sh -c 'set -eu; cargo clean --manifest-path rust/Cargo.toml; make check'
inspect the job's lambda expression
(lambda()
  `((task . ("maak-test"))
    (project . "lambdock")
    (branch-name . "trunk")
    (clone-url . "https://github.com/jjba23/lambdock.git")))