lambdock-6d3212a1-f01d

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 2068e8d to bff0422
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 succeeded33 lines · 0.0s
commit bff04225f7ac2331c2b6db563214d8e640a0f475
Author: Josep Bigorra <jjbigorra@gmail.com>
Date:   Mon Nov 16 12:18:49 2026 +0100

    refactor(ui): decide which stack files deserve a thumbnail from Rust
    
    The last pure decision in ui/stack.c: a file is worth decoding when it is a regular
    file, under 32 MiB, an image GdkPixbuf can actually read, and under 80 megapixels.
    Reading an image header is cheap, which is why the decision happens before the
    decode and why it belongs before the worker queue rather than inside it.
    
    It is tested with a real one-pixel PNG written as literal bytes -- the format, not a
    library call, so nothing has to be installed to create one -- alongside the cases
    that should not decode: a text file with a picture's name, a directory, a missing
    file, an empty file, and a sparse file just over the size cap whose contents are
    never read.
    
    The header reader is called through GdkPixbuf's own C entry point: the crate does
    not depend on gdk-pixbuf directly, the library is linked through GTK already, and
    only the type of the format it returns is discarded.
    
    The test fixture also got the file it was missing: tests/xdg-config had only
    gtk-3.0/settings.ini, so the icon-theme pin every C test relies on did nothing for a
    GTK 4 binary, which reads gtk-4.0/settings.ini. The 4.0 file is there now, with a
    README saying why both exist. On this host the two binaries that need
    utilities-terminal still abort -- its Adwaita install is incomplete -- so the pin is
    correct now but unverified here.
    
    Suite: 266 Rust tests; 33/37 meson tests, the three failures being the ones this host
    already had.

M       rust/src/ui/stack.rs
M       src/ui/stack.c
A       tests/xdg-config/README
A       tests/xdg-config/gtk-4.0/settings.ini
testmaak test failed105 lines · 2.1s
The Meson build system
Version: 1.9.0
Source dir: /etc/byggsteg/job-clone/lambdock/trunk
Build dir: /etc/byggsteg/job-clone/lambdock/trunk/build
Build type: native build
Project name: lambdock
Project version: 1.4.0
C compiler for the host machine: cc (gcc 14.3.0 "cc (GCC) 14.3.0")
C linker for the host machine: cc ld.bfd 2.44
Host machine cpu family: x86_64
Host machine cpu: x86_64
Compiler for C supports arguments -Wpedantic: YES 
Compiler for C supports arguments -Wshadow: YES 
Compiler for C supports arguments -Wstrict-prototypes: YES 
Compiler for C supports arguments -Wmissing-prototypes: YES 
Compiler for C supports arguments -Wredundant-decls: YES 
Compiler for C supports arguments -Wimplicit-fallthrough: YES 
Compiler for C supports arguments -Wvla: YES 
Compiler for C supports arguments -Wundef: YES 
Compiler for C supports arguments -Wformat=2: YES 
Compiler for C supports arguments -Wformat-security: YES 
Compiler for C supports arguments -Werror=implicit-function-declaration: YES 
Compiler for C supports arguments -Werror=incompatible-pointer-types: YES 
Compiler for C supports arguments -Werror=int-conversion: YES 
Compiler for C supports arguments -Wno-overlength-strings: YES 
Found pkg-config: YES (/gnu/store/g4q6gg96i463yk5jw7hrw6yvf5168czg-profile/bin/pkg-config) 0.29.2
Run-time dependency gtk4 found: YES 4.22.1
Run-time dependency guile-3.0 found: YES 3.0.9
Run-time dependency gtk4-layer-shell-0 found: YES 1.3.0
Run-time dependency wayland-client found: YES 1.26.0
Run-time dependency gtk4-x11 found: YES 4.22.1
Library m found: YES
Run-time dependency wlr-protocols found: YES 1.0
Program wayland-scanner found: YES (/gnu/store/g4q6gg96i463yk5jw7hrw6yvf5168czg-profile/bin/wayland-scanner)
Build-time dependency gio-2.0 found: YES 2.86.5
Program glib-compile-resources found: YES (/gnu/store/g4q6gg96i463yk5jw7hrw6yvf5168czg-profile/bin/glib-compile-resources)
Program desktop-file-validate found: NO
Message: desktop-file-validate not found: skipping desktop entry validation
Program appstreamcli found: NO
Message: appstreamcli not found: skipping AppStream metadata validation
Program msgfmt found: YES (/gnu/store/g4q6gg96i463yk5jw7hrw6yvf5168czg-profile/bin/msgfmt)
Program msginit found: YES (/gnu/store/g4q6gg96i463yk5jw7hrw6yvf5168czg-profile/bin/msginit)
Program msgmerge found: YES (/gnu/store/g4q6gg96i463yk5jw7hrw6yvf5168czg-profile/bin/msgmerge)
Program xgettext found: YES (/gnu/store/g4q6gg96i463yk5jw7hrw6yvf5168czg-profile/bin/xgettext)
Program cargo found: YES (/gnu/store/g4q6gg96i463yk5jw7hrw6yvf5168czg-profile/bin/cargo)
Program rust/cargo-build.sh found: YES (/etc/byggsteg/job-clone/lambdock/trunk/rust/cargo-build.sh)
Run-time dependency glib-2.0 found: YES 2.86.5
Dependency glib-2.0 found: YES 2.86.5 (cached)
Dependency gio-2.0 found: YES 2.86.5 (cached)
Dependency glib-2.0 found: YES 2.86.5 (cached)
Dependency glib-2.0 found: YES 2.86.5 (cached)
Dependency glib-2.0 found: YES 2.86.5 (cached)
Dependency glib-2.0 found: YES 2.86.5 (cached)
Dependency glib-2.0 found: YES 2.86.5 (cached)
Dependency glib-2.0 found: YES 2.86.5 (cached)
Dependency glib-2.0 found: YES 2.86.5 (cached)
Dependency glib-2.0 found: YES 2.86.5 (cached)
Dependency gio-2.0 found: YES 2.86.5 (cached)
Dependency glib-2.0 found: YES 2.86.5 (cached)
Dependency gio-2.0 found: YES 2.86.5 (cached)
Dependency glib-2.0 found: YES 2.86.5 (cached)
Program guile found: YES (/gnu/store/g4q6gg96i463yk5jw7hrw6yvf5168czg-profile/bin/guile)
Program tests/run_scheme_tests.sh found: YES (/etc/byggsteg/job-clone/lambdock/trunk/tests/run_scheme_tests.sh)
Build targets in project: 49

Found ninja-1.13.2 at /gnu/store/g4q6gg96i463yk5jw7hrw6yvf5168czg-profile/bin/ninja
ninja: Entering directory `build'
[1/256] Generating wlr-foreign-toplevel-protocol-c with a custom command
[2/256] Generating wlr-foreign-toplevel-protocol-h with a custom command
[3/256] Generating lambdock-resources_h with a custom command
[3/256] Generating lambdock-rust with a custom command (wrapped by meson to set env)
error: failed to calculate checksum of: /etc/byggsteg/job-clone/lambdock/trunk/rust/vendor/system-deps/src/tests/test.tar.gz

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

Caused by:
  No such file or directory (os error 2)
[4/256] Generating lambdock-resources_c with a custom command
FAILED: [code=101] liblambdock.a 
env CARGO_HOME=/etc/byggsteg/job-clone/lambdock/trunk/build/rust-cargo-home /etc/byggsteg/job-clone/lambdock/trunk/rust/cargo-build.sh /etc/byggsteg/job-clone/lambdock/trunk/rust/Cargo.toml /etc/byggsteg/job-clone/lambdock/trunk/build/rust-target release liblambdock.a
[6/256] Compiling C object lambdock.p/meson-generated_.._lambdock-resources.c.o
ninja: build stopped: subcommand failed.


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

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 `ninja' would execute
outside the Guix environment.

The GTK tests need a display: with none, `gtk_init_check' fails and GLib turns
the resulting GTK warnings into aborts (6 of 7 tests die with SIGTRAP), so the
suite runs on a virtual X server, as in package.nix's checkPhase.`GDK_BACKEND', `GTK_A11Y' and `GSK_RENDERER' are pinned because there is no compositor, no a11y
bus and no EGL under Xvfb; `GTK_A11Y=test' is GTK's own backend for the
accessible-name assertions in the suite.

The build directory is thrown away first: the Byggsteg job clone survives
between jobs, and a tree configured by a different Meson version makes both
`meson setup' and `ninja' fail with 'build data file ... references functions
or classes that don't exist'. Rebuilding from scratch also means the passing
tests are the ones that match the checked out sources.

  Execute command:
guix time-machine --channels=channels.scm -- shell -m manifest.scm -- /bin/sh -c 'set -eu; export GTK_A11Y=test GDK_BACKEND=x11 GSK_RENDERER=cairo; rm -rf build; meson setup build; ninja -C build; xvfb-run -a -s "-screen 0 1024x768x24" meson test -C build --print-errorlogs'

Executing: guix time-machine --channels=channels.scm -- shell -m manifest.scm -- /bin/sh -c 'set -eu; export GTK_A11Y=test GDK_BACKEND=x11 GSK_RENDERER=cairo; rm -rf build; meson setup build; ninja -C build; xvfb-run -a -s "-screen 0 1024x768x24" meson test -C build --print-errorlogs'

maak: error: command failed (exit code 101): guix time-machine --channels=channels.scm -- shell -m manifest.scm -- /bin/sh -c 'set -eu; export GTK_A11Y=test GDK_BACKEND=x11 GSK_RENDERER=cairo; rm -rf build; meson setup build; ninja -C build; xvfb-run -a -s "-screen 0 1024x768x24" meson test -C build --print-errorlogs'
        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 . "lambdock")
    (branch-name . "trunk")
    (clone-url . "https://github.com/jjba23/lambdock.git")))