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.
