Source: pyrit Version: 0.4.0-7 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161219 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): > Traceback (most recent call last): > File "test_pyrit.py", line 311, in testVerify > self._computeDatabase(storage, 'test') > File "test_pyrit.py", line 159, in _computeDatabase > with cpyrit.cpyrit.StorageIterator(storage, essid) as dbiter: > File "/<<PKGBUILDDIR>>/.pybuild/pythonX.Y_2.7/build/cpyrit/cpyrit.py", line > 727, in __init__ > self.cp = CPyrit() if yieldNewResults else None > File "/<<PKGBUILDDIR>>/.pybuild/pythonX.Y_2.7/build/cpyrit/cpyrit.py", line > 462, in __init__ > self.cores.append(CPUCore(queue=self)) > TypeError: _cpyrit_cpu.CPUDevice.__new__(CPUCore) is not safe, use > object.__new__() > > Ran 24 tests in 1.890s > > FAILED (errors=16) > Testing with filesystem-storage... > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://aws-logs.debian.net/2016/12/19/pyrit_0.4.0-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.
