Your message dated Sun, 1 Jan 2017 18:06:15 +0100
with message-id <20170101170615.vvhyu4bfoikya...@xanadu.blop.info>
and subject line Re: Bug#844147: ck: FTBFS: build timeout
has caused the Debian Bug report #844147,
regarding ck: FTBFS: build timeout
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.)
--
844147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ck
Version: 0.4.4-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/regressions/ck_brlock/validate'
>
> ----[ Testing bytelock....
> make[3]: Entering directory
> '/<<PKGBUILDDIR>>/regressions/ck_bytelock/validate'
> ./validate 64 1
> Creating threads (mutual exclusion)...done
> Waiting for threads to finish correctness regression...E: Caught signal
> ‘Terminated’: terminating immediately
> Makefile:121: recipe for target 'check' failed
> make[2]: *** [check] Terminated
> Makefile:31: recipe for target 'check' failed
> make[1]: *** [check] Terminated
> debian/rules:7: recipe for target 'binary' failed
> make: *** [binary] Terminated
> Makefile:11: recipe for target 'check' failed
> make[3]: *** [check] Terminated
> E: Build killed with signal TERM after 150 minutes of inactivity
The full build log is available from:
http://aws-logs.debian.net/2016/11/11/ck_0.4.4-1_unstable.log
This failure happens on a CPU with TSX extensions available, but is not
reproducible on a machine without them. For context, I recommend reading the
thread starting at https://lists.debian.org/debian-devel/2016/11/msg00210.html
The node used is an Amazon EC2 VM with 64 cores. /proc/cpuinfo says:
model : 79
model name : Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz
stepping : 1
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.5.2-2
Hi,
On 29/12/16 at 17:22 -0500, Robert Edmonds wrote:
> Lucas Nussbaum wrote:
> > Hi,
> >
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
>
> > The full build log is available from:
> > http://aws-logs.debian.net/2016/11/11/ck_0.4.4-1_unstable.log
> >
> > This failure happens on a CPU with TSX extensions available, but is not
> > reproducible on a machine without them. For context, I recommend reading the
> > thread starting at
> > https://lists.debian.org/debian-devel/2016/11/msg00210.html
> >
> > The node used is an Amazon EC2 VM with 64 cores. /proc/cpuinfo says:
> > model : 79
> > model name : Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz
> > stepping : 1
>
> Hi, Lucas:
>
> If I understand the upstream source correctly, TSX support is not
> enabled unless --enable-rtm is explicitly passed to the configure
> script, which we don't do for the Debian build. According to your build
> log, RTM is disabled:
>
> RTM = CK_MD_RTM_DISABLE
>
> So I'm confused as to how TSX support in the build system's CPU could be
> the cause. I think your FTBFS might actually be due to #764827 ("ck:
> upper bound on cores being used in tests"). It looks like building on
> systems with a high number of cores can cause the test suite to take an
> unreasonable amount of time, so I've uploaded 0.5.2-2 which limits the
> number of cores used to a small value.
>
> Could you retry your build with ck >= 0.5.2-2 once it hits the archive?
I can confirm that it builds fine now, thanks!
Lucas
--- End Message ---
