starting new job...
→ running command: cd "/etc/byggsteg/job-clone//lucidplan/trunk" && git reset --hard && git pull
HEAD is now at c06fd81 docs: README update
From https://codeberg.org/jjba23/lucidplan
c06fd81..927d958 trunk -> origin/trunk
Updating c06fd81..927d958
Fast-forward
manifest.scm | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
→ running command: cd /etc/byggsteg/job-clone/lucidplan/trunk && uname -a
Linux wolk-jjba 7.1.5-gnu #1 SMP PREEMPT_DYNAMIC 1 x86_64 GNU/Linux
→ running command: cd /etc/byggsteg/job-clone/lucidplan/trunk && git log --name-status HEAD^..HEAD
commit 927d9586918f04fb82d7b5216fbf812b262d8dfb
Author: Josep Bigorra <jjbigorra@gmail.com>
Date: Tue Oct 20 14:02:00 2026 +0200
chore: Update guile-veritas
M manifest.scm
→ running command: cd /etc/byggsteg/job-clone/lucidplan/trunk && maak test
The following derivation will be built:
/gnu/store/m4hzsag10rgm8ijqslc8q47xccq0gyx2-profile.drv
building CA certificate bundle...
listing Emacs sub-directories...
building fonts directory...
building directory of Info manuals...
building profile with 21 packages...
Backtrace:
In ice-9/boot-9.scm:
1784:12 17 (with-exception-handler _ _ #:unwind? _ #:unwind-for-type _)
In unknown file:
16 (apply-smob/0 #<thunk 7faffac57340>)
In ice-9/boot-9.scm:
733:2 15 (call-with-prompt _ _ #<procedure default-prompt-handler (k proc)>)
In ice-9/eval.scm:
619:8 14 (_ #(#(#<directory (guile-user) 7faffac5ac80>)))
In ice-9/command-line.scm:
187:19 13 (_ #<input: custom-port 7faffac413f0>)
In unknown file:
12 (eval ((@ (veritas runner) run-tests)) #<directory (guile-user) 7faffac5ac80>)
In veritas/runner.scm:
434:16 11 (run-tests)
In srfi/srfi-1.scm:
750:9 10 (for-each #<procedure 7faff7d24b80 at veritas/runner.scm:434:26 (file)> ("ticket-triage-spec.scm"))
In veritas/runner.scm:
64:13 9 (run-test-file #:test-file _ #:test-type _ #:entrypoint-function _)
In ice-9/threads.scm:
399:8 8 (_ _)
In ice-9/boot-9.scm:
3307:13 7 (_)
In ice-9/threads.scm:
399:8 6 (_ _)
In ice-9/boot-9.scm:
3596:20 5 (_)
2890:4 4 (save-module-excursion _)
3616:26 3 (_)
In unknown file:
2 (primitive-load-path "veritas/unit/ticket-triage-spec" #<procedure 7faff7d24660 at ice-9/boot-9.scm:3603:37 ()>)
In test/veritas/unit/ticket-triage-spec.scm:
55:9 1 (_)
55:9 0 (_)
test/veritas/unit/ticket-triage-spec.scm:55:9: Wrong type to apply: #<syntax-transformer test>
scanning directories for unit tests...
scanning present working directory for unit tests...
shuffled the files with seed 655893024 (replay with VERITAS_SEED=655893024)
found unit tests: (ticket-triage-spec.scm)
running unit tests from file: ticket-triage-spec.scm, entrypoint: spec
Backtrace:
In ice-9/boot-9.scm:
1784:12 7 (with-exception-handler _ _ #:unwind? _ #:unwind-for-type _)
In unknown file:
6 (apply-smob/0 #<thunk 7f46d077f340>)
In ice-9/boot-9.scm:
733:2 5 (call-with-prompt _ _ #<procedure default-prompt-handler (k proc)>)
In ice-9/eval.scm:
619:8 4 (_ #(#(#<directory (guile-user) 7f46d0782c80>)))
In ice-9/command-line.scm:
187:19 3 (_ #<input: custom-port 7f46d076a3f0>)
In unknown file:
2 (eval ((@ (maak main) main)) #<directory (guile-user) 7f46d0782c80>)
In srfi/srfi-1.scm:
750:9 1 (for-each #<procedure 7f46ce867198 at maak/maak.scm:87:12 (task)> (test))
In maak/dsl.scm:
89:12 0 ($ _ #:verbose? _ #:join _)
maak/dsl.scm:89:12: In procedure $:
Non-zero exit code when running!
Command: guix time-machine --channels=channels.scm -- shell -m manifest.scm -- env VERITAS_TEST_TYPE=unit VERITAS_RUN_BENCHMARKS=true guile -L . -L lib -L test -c '((@ (veritas runner) run-tests))'
Exit code: 1
--------------------------------------------------------------
Maak: the infinitely extensible command runner
Loading tasks from Maak file: /etc/byggsteg/job-clone/lucidplan/trunk/maak.scm
Executing Maak tasks: test
--------------------------------------------------------------
=> Running Maak task: test
Run the test suite with veritas.
The tests live under `test/veritas/': `unit/' for the ones that run on every
change, and `benchmark/' for the ones that measure rather than assert, which
veritas keeps apart because they answer a different question and take a
different amount of time. The application's own directories are on the load
path, so a test names the module it tests the way the application does.