Source: grpc Version: 0.12.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160714 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): > /«PKGBUILDDIR»/bins/opt/httpscli_test(+0x3197a)[0x7f013074097a] > /«PKGBUILDDIR»/bins/opt/httpscli_test(+0x46e77)[0x7f0130755e77] > /lib/x86_64-linux-gnu/libpthread.so.0(+0x7464)[0x7f012f9a8464] > /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f012ec0330d] > Aborted > test httpscli_test failed > make[2]: *** [test_c] Error 1 > Makefile:3287: recipe for target 'test_c' failed > make[2]: Leaving directory '/«PKGBUILDDIR»' > make[1]: *** [override_dh_auto_test] Error 2 > debian/rules:22: recipe for target 'override_dh_auto_test' failed > make[1]: Leaving directory '/«PKGBUILDDIR»' > make: *** [build-arch] Error 2 > debian/rules:29: recipe for target 'build-arch' failed > dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 > Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://people.debian.org/~lucas/logs/2016/07/14/grpc_0.12.0-1_unstable_gcc5.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.
