Your message dated Tue, 26 Mar 2019 22:02:15 +0100
with message-id <20190326210215.frm6qrwfuh2uu...@xanadu.blop.info>
and subject line Re: Bug#924808: lua-nvim: FTBFS: E: Build killed with signal
TERM after 150 minutes of inactivity
has caused the Debian Bug report #924808,
regarding lua-nvim: FTBFS: E: Build killed with signal TERM after 150 minutes
of inactivity
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
924808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-nvim
Version: 0.1.0-1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190315 qa-ftbfs
Justification: FTBFS in buster on amd64
Hi,
During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
> [ RUN ] test/session_spec.lua @ 35: Session using ChidProcessStream can
> make requests to nvim
> [ OK ] test/session_spec.lua @ 35: Session using ChidProcessStream can
> make requests to nvim (3.10 ms)
> [ RUN ] test/session_spec.lua @ 40: Session using ChidProcessStream can
> get api metadata
> [ OK ] test/session_spec.lua @ 40: Session using ChidProcessStream can
> get api metadata (5.43 ms)
> [ RUN ] test/session_spec.lua @ 50: Session using ChidProcessStream can
> receive messages from nvim
> [ OK ] test/session_spec.lua @ 50: Session using ChidProcessStream can
> receive messages from nvim (4.48 ms)
> [ RUN ] test/session_spec.lua @ 58: Session using ChidProcessStream can
> receive requests from nvim
> [ OK ] test/session_spec.lua @ 58: Session using ChidProcessStream can
> receive requests from nvim (6.09 ms)
> [ RUN ] test/session_spec.lua @ 96: Session using ChidProcessStream can
> deal with recursive requests from nvim
> [ OK ] test/session_spec.lua @ 96: Session using ChidProcessStream can
> deal with recursive requests from nvim (5.25 ms)
> [ RUN ] test/session_spec.lua @ 116: Session using ChidProcessStream can
> receive errors from nvim
> [ OK ] test/session_spec.lua @ 116: Session using ChidProcessStream can
> receive errors from nvim (4.73 ms)
> [ RUN ] test/session_spec.lua @ 130: Session using ChidProcessStream can
> break out of event loop with a timeout
> [ OK ] test/session_spec.lua @ 130: Session using ChidProcessStream can
> break out of event loop with a timeout (50.79 ms)
> [ RUN ] test/session_spec.lua @ 35: Session using SocketStream
> [/tmp/nvim.socket-9155] can make requests to nvim
> E: Build killed with signal TERM after 150 minutes of inactivity
The full build log is available from:
http://aws-logs.debian.net/2019/03/15/lua-nvim_0.1.0-1-1_testing.log
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!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 0.1.0-1-2
On 17/03/19 at 23:40 +0100, Santiago Vila wrote:
> On Sun, Mar 17, 2019 at 07:09:44PM +0100, Lucas Nussbaum wrote:
> > Source: lua-nvim
> > Version: 0.1.0-1-1
> > Severity: serious
> > Tags: buster sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20190315 qa-ftbfs
> > Justification: FTBFS in buster on amd64
>
> Hello Lucas. I was able to reproduce this hang too, but I believe it's
> fixed in 0.1.0-1-2 which is now in testing. Can you double-check with
> version 0.1.0-1-2?
Yes, it works with 0.1.0-1-2. Closing.
Thanks!
Lucas
--- End Message ---
