Your message dated Mon, 26 Dec 2016 14:24:15 +0100
with message-id <[email protected]>
and subject line Re: Bug#848780: pyrit: FTBFS: E: Build killed with signal TERM
after 150 minutes of inactivity
has caused the Debian Bug report #848780,
regarding pyrit: FTBFS: E: Build killed with signal TERM after 150 minutes of
inactivity
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
848780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848780
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pyrit
Version: 0.4.0-7
Severity: serious
Tags: stretch sid
User: [email protected]
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.
--- End Message ---
--- Begin Message ---
On 2016-12-19 22:23, Lucas Nussbaum wrote:
> Source: pyrit
> Version: 0.4.0-7
> Severity: serious
> Tags: stretch sid
> User: [email protected]
> 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
As reported by Sophie in #849060, this was apparently caused by
python2.7 version 2.7.13~rc1-1 and has been resolved with version 2.7.13-1.
I can't reproduce this particular FTBFS anymore, so I assume this was
indeed the case and I'll therefore close the bug.
A new FTBFS popped, but this is in relation to the recent update of
python-scapy from 2.3.2 to 2.3.3.
Regards,
Christian
signature.asc
Description: OpenPGP digital signature
--- End Message ---
