lambdock-a7e6ecfb-f969

job failed

starting new job...
rundir='/etc/byggsteg/job-clone//lambdock/trunk succeeded43 lines · 0.6s
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 95b9c1c to 0d5d9fb
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 succeeded31 lines · 0.0s
commit 0d5d9fb1b4d6662ca081dfc075d14a63e316226d
Author: Josep Bigorra <jjbigorra@gmail.com>
Date:   Mon Nov 16 18:25:04 2026 +0100

    fix: the installer understands an empty DESTDIR, and builds what it copies
    
    The Guix build reached the install phase and stopped:
    
        could not install .../rust/target/release/lambdock to
        gnu/store/.../bin/lambdock: No such file or directory
    
    Two bugs in one message. An empty `--destdir` -- which is how Guix calls it, with
    `--prefix $out` -- made the installer strip the prefix's leading slash and build a
    *relative* path, so it tried to write `gnu/store/...` under the build directory.
    And it copied a release binary that no phase had built, because the test phase is
    the only one that runs cargo.
    
    `install` now treats an empty staging directory as the prefix itself, and builds
    the release binary when it is not there: `cargo xtask install` is the whole
    install step of every recipe, so it cannot assume somebody built first. The Guix
    recipe names that build phase explicitly as well.
    
    Verified both shapes by hand: `--prefix /tmp/p1` lands in `/tmp/p1/bin/lambdock`,
    and `--prefix /usr/local --destdir /tmp/d1` in `/tmp/d1/usr/local/bin/lambdock`.
    
    Suite: cargo test green (312 Rust tests and the Scheme suite), and the lock is
    refreshed for the version bump.

M       Cargo.lock
M       NEWS.org
M       guix.scm
M       rust/Cargo.toml
M       xtask/src/main.rs
testmaak test failed24 lines · 0.3s
     Removed 0 files
make: *** No rule to make target 'check'.  Stop.

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")))