Bug#1020029: emacs-deferred: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Source: emacs-deferred
Version: 0.5.1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> ert-run-or-rerun-test(#s(ert--stats :selector t :tests ... :test-map
> ert-run-tests(t #f(compiled-function (event-type &rest event-args) #
> ert-run-tests-batch(nil)
> ert-run-tests-batch-and-exit()
> command-line-1(("-l" "package" "--eval" "(add-to-list 'package-direc
> command-line()
> normal-top-level()
> Test deferred-main-chain condition:
> (error "Cannot find suitable directory for output in ‘native-comp-eln-load-path’")
> FAILED 9/18 deferred-main-chain (0.080718 sec)
> passed 10/18 deferred-parallel (0.232513 sec)
> passed 11/18 deferred-primitive-compile (0.018742 sec)
> passed 12/18 deferred-primitive-scope (0.000085 sec)
> passed 13/18 deferred-primitive-simple (0.000100 sec)
> deferred error : (wrong-number-of-arguments #<subr start-process-shell-command> 4)
> E: Build killed with signal TERM after 150 minutes of inactivity
The full build log is available from:
http://qa-logs.debian.net/2022/09/17/emacs-deferred_0.5.1-4_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220917&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
Reply to: