Your message dated Sat, 26 Dec 2020 21:36:53 +0100
with message-id <[email protected]>
and subject line Re: Bug#952614: dropwatch: FTBFS: E: Build killed with signal
TERM after 150 minutes of inactivity
has caused the Debian Bug report #952614,
regarding dropwatch: 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 [email protected]
immediately.)
--
952614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952614
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: dropwatch
Version: 1.5.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200225 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules).
Relevant part (hopefully):
> make[2]: Nothing to be done for 'check'.
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/src'
> Making check in doc
> make[2]: Entering directory '/<<PKGBUILDDIR>>/doc'
> make[2]: Nothing to be done for 'check'.
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/doc'
> Making check in tests
> make[2]: Entering directory '/<<PKGBUILDDIR>>/tests'
> make rundropwatch.sh
> make[3]: Entering directory '/<<PKGBUILDDIR>>/tests'
> make[3]: Nothing to be done for 'rundropwatch.sh'.
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/tests'
> make check-TESTS
> make[3]: Entering directory '/<<PKGBUILDDIR>>/tests'
> make[4]: Entering directory '/<<PKGBUILDDIR>>/tests'
> E: Build killed with signal TERM after 150 minutes of inactivity
The full build log is available from:
http://qa-logs.debian.net/2020/02/25/dropwatch_1.5.1-2_unstable.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 ---
On 26/02/20 at 17:13 +0100, Lucas Nussbaum wrote:
> Source: dropwatch
> Version: 1.5.1-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200225 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
Hi,
In the same setup, I can no longer reproduce this problem, so I'm
closing this bug.
Lucas
--- End Message ---
