lambdock-403161c9-0c88

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 f6790a1 to 21041e3
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 succeeded37 lines · 0.0s
commit 21041e3bdf435218f588790d8c8a3f4cc8d5f922
Author: Josep Bigorra <jjbigorra@gmail.com>
Date:   Mon Nov 16 11:22:02 2026 +0100

    refactor(ui): answer the menu's keyboard from Rust
    
    The first half of ui/popover_menu.c moves: Escape dismissal, the arrow keys, Home
    and End, and where the focus lands when the menu opens. All of it walks the
    popover's own widget tree and needs nothing from the dock, which is exactly the
    seam this module splits on -- the menu's *content* (rows, sections and their
    callbacks) stays in C for its own step.
    
    The two rules that were easy to lose are both kept. The controllers live on the
    popover, so a reload that rebuilds the menu's contents does not stack a second
    set: the marker is set on the popover, and a marker on the controller too, because
    that is what a caller can look up by name (tests/test_popover_menu.c does). And
    they only act on an item menu -- a stack panel reuses the same popover and has its
    own arrow handling, so the row walk refuses a child without the menu class.
    
    Two things the port had to learn: gtk-rs asserts its own initialization flag inside
    the controller machinery, so both entry points call ui::ensure_gtk_initialized()
    like every other Rust entry point that touches a widget; and the focus walk has to
    stop at the popover, or a focused label inside a row would never resolve to the row
    above it.
    
    There are no cargo tests here on purpose: every decision needs a popover with rows
    in it and a window to hold the focus, and cargo test stays display-free. The C
    suite carries them -- escape_controller and keyboard pass unchanged, along with the
    other 16 subtests.
    
    Suite: 255 Rust tests; 33/37 meson tests, with the same three failures this host
    already had.

M       HACKING.org
M       NEWS.org
M       meson.build
M       rust/src/ui/mod.rs
A       rust/src/ui/popover_menu.rs
M       src/ui/popover_menu.c
testmaak test failed105 lines · 1.8s
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/271] Generating wlr-foreign-toplevel-protocol-c with a custom command
[2/271] Generating wlr-foreign-toplevel-protocol-h with a custom command
[3/271] Generating lambdock-resources_h with a custom command
[3/271] 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.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)
[4/271] 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/271] 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")))