Control: tags -1 + help Control: severity -1 important On 19.11.2016 07:27, Lucas Nussbaum wrote: > Source: python3.5 > Version: 3.5.2-7 > Severity: serious > Tags: stretch sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20161118 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): >> data = self.socket.recv(buffer_size) >> File "/<<PKGBUILDDIR>>/Lib/ssl.py", line 922, in recv >> return self.read(buflen) >> File "/<<PKGBUILDDIR>>/Lib/ssl.py", line 799, in read >> return self._sslobj.read(len, buffer) >> File "/<<PKGBUILDDIR>>/Lib/ssl.py", line 585, in read >> v = self._sslobj.read(len) >> OSError: [Errno 0] Error >> E: Caught signal ‘Terminated’: terminating immediately >> Makefile:526: recipe for target 'run_profile_task' failed >> make[2]: *** [run_profile_task] Terminated >> Makefile:504: recipe for target 'profile-opt' failed >> make[1]: *** [profile-opt] Terminated >> debian/rules:274: recipe for target 'stamps/stamp-build-static' failed >> make: *** [stamps/stamp-build-static] 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/18/python3.5_3.5.2-7_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.
I am unable to reproduce this, and the recent 3.5.2-8 upload built sucessfully on all buildds.
