Source: node-groove Version: 2.5.0-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[1]: Leaving directory '/<<PKGBUILDDIR>>' > debian/rules override_dh_auto_test > make[1]: Entering directory '/<<PKGBUILDDIR>>' > mocha --reporter spec > > [0m[0m > [32m ✓[0m[90m version [0m > [32m ✓[0m[90m logging [0m > [32m ✓[0m[90m open fails for bogus file [0m > [32m ✓[0m[90m open file and read metadata [0m > [32m ✓[0m[90m update metadata [0m > [32m ✓[0m[90m create empty playlist [0m > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > [32m ✓[0m[90m create empty player [0m > [32m ✓[0m[90m playlist item ids [0m > debian/rules:20: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/2016/11/11/node-groove_2.5.0-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.
