Your message dated Wed, 12 Nov 2014 12:01:08 +0100
with message-id <[email protected]>
and subject line Re: Bug#769241: python-crypto: FTBFS in jessie/i386: Tests
failures
has caused the Debian Bug report #769241,
regarding python-crypto: FTBFS in jessie/i386: Tests failures
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.)
--
769241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769241
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: python-crypto
Version: 2.6.1-5
Severity: serious
Tags: jessie sid
User: [email protected]
Usertags: qa-ftbfs-20141112 qa-ftbfs
Justification: FTBFS in jessie on i386
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on i386.
Relevant part (hopefully):
> core.setup(**kw)
> File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
> dist.run_commands()
> File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
> self.run_command(cmd)
> File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
> cmd_obj.run()
> File "setup.py", line 331, in run
> SelfTest.run(module=moduleObj, verbosity=self.verbose, stream=sys.stdout,
> config=self.config)
> File
> "/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/Crypto/SelfTest/__init__.py",
> line 76, in run
> raise SelfTestError("Self-test failed", result)
> Crypto.SelfTest.SelfTestError: ('Self-test failed',
> <unittest.runner.TextTestResult run=1071 errors=1 failures=0>)
> E: pybuild pybuild:256: test: plugin custom failed with: exit code=1:
> python2.7 setup.py test
> dh_auto_test: pybuild --test -i python{version} -p 2.7 -s custom
> --test-args={interpreter} setup.py test --dir . returned exit code 13
> make[1]: *** [override_dh_auto_test] Error 13
> debian/rules:21: recipe for target 'override_dh_auto_test' failed
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/11/12/python-crypto_2.6.1-5_jessie-i386.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 12/11/14 at 11:41 +0100, Sebastian Ramacher wrote:
> Control: severity -1 important
> Control: tags -1 moreinfo unreproducible
>
> On 2014-11-12 11:21:47, Lucas Nussbaum wrote:
> > Source: python-crypto
> > Version: 2.6.1-5
> > Severity: serious
> > Tags: jessie sid
> > User: [email protected]
> > Usertags: qa-ftbfs-20141112 qa-ftbfs
> > Justification: FTBFS in jessie on i386
> >
> > Hi,
> >
> > During a rebuild of all packages in jessie (in a jessie chroot, not a
> > sid chroot), your package failed to build on i386.
> >
> > Relevant part (hopefully):
> > > core.setup(**kw)
> > > File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
> > > dist.run_commands()
> > > File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
> > > self.run_command(cmd)
> > > File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
> > > cmd_obj.run()
> > > File "setup.py", line 331, in run
> > > SelfTest.run(module=moduleObj, verbosity=self.verbose,
> > > stream=sys.stdout, config=self.config)
> > > File
> > > "/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/Crypto/SelfTest/__init__.py",
> > > line 76, in run
> > > raise SelfTestError("Self-test failed", result)
> > > Crypto.SelfTest.SelfTestError: ('Self-test failed',
> > > <unittest.runner.TextTestResult run=1071 errors=1 failures=0>)
> > > E: pybuild pybuild:256: test: plugin custom failed with: exit code=1:
> > > python2.7 setup.py test
> > > dh_auto_test: pybuild --test -i python{version} -p 2.7 -s custom
> > > --test-args={interpreter} setup.py test --dir . returned exit code 13
> > > make[1]: *** [override_dh_auto_test] Error 13
> > > debian/rules:21: recipe for target 'override_dh_auto_test' failed
>
> The relevant part is:
> | ======================================================================
> | ERROR: runTest
> (Crypto.SelfTest.Random.test__UserFriendlyRNG.RNGMultiprocessingForkTest)
> | ----------------------------------------------------------------------
> | Traceback (most recent call last):
> | File
> "/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/Crypto/SelfTest/Random/test__UserFriendlyRNG.py",
> line 146, in runTest
> | pool = multiprocessing.Pool(processes=n_procs,
> initializer=Crypto.Random.atfork)
> | File "/usr/lib/python2.7/multiprocessing/__init__.py", line 232, in Pool
> | return Pool(processes, initializer, initargs, maxtasksperchild)
> | File "/usr/lib/python2.7/multiprocessing/pool.py", line 138, in __init__
> | self._setup_queues()
> | File "/usr/lib/python2.7/multiprocessing/pool.py", line 234, in
> _setup_queues
> | self._inqueue = SimpleQueue()
> | File "/usr/lib/python2.7/multiprocessing/queues.py", line 352, in __init__
> | self._rlock = Lock()
> | File "/usr/lib/python2.7/multiprocessing/synchronize.py", line 147, in
> __init__
> | SemLock.__init__(self, SEMAPHORE, 1, 1)
> | File "/usr/lib/python2.7/multiprocessing/synchronize.py", line 75, in
> __init__
> | sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue)
> | OSError: [Errno 13] Permission denied
>
> I cannot reproduce it. Looks like the chroot is broken somehow. Why is
> /dev/shm not usable in the chroot?
>
> Reducing severity and tagging accordingly.
Ah, yes, I need to fix that, and missed that the failure was caused by
that. Closing.
Lucas
signature.asc
Description: Digital signature
--- End Message ---
