[Python-modules-team] Bug#860663: Bug#860663: pytest: FTBFS on i386: segfault during tests
On 19/04/17 at 20:42 +0200, Sebastian Ramacher wrote:
> Control: tags -1 + moreinfo unreproducible
>
> On 2017-04-19 09:26:48, Lucas Nussbaum wrote:
> > Source: pytest
> > Version: 3.0.6-1
> > Severity: serious
> > Tags: stretch sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
> > Justification: FTBFS in stretch on i386
> >
> > Hi,
> >
> > During a rebuild of all packages in stretch (in a stretch chroot, not a
> > sid chroot), your package failed to build on i386.
> >
> > Relevant part (hopefully):
> > > ../../../testing/test_pluginmanager.py ...
> > > ../../../testing/test_pytester.py x...
> > > ../../../testing/test_recwarn.py ..
> > > ../../../testing/test_resultlog.py ...
> > > ../../../testing/test_runner.py
> > > ...sss.....x...
> > > ../../../testing/test_runner_xunit.py ...
> > > ../../../testing/test_session.py .
> > > ../../../testing/test_skipping.py
> > > ..x..
> > > ../../../testing/test_terminal.py
> > > ..s..s.
> > > ../../../testing/test_tmpdir.py ...s
> > > ../../../testing/test_unittest.py
> > >
> > > ../../../testing/code/test_code.py ..
> > > ../../../testing/code/test_excinfo.py Segmentation fault
> > > E: pybuild pybuild:283: test: plugin custom failed with: exit code=139:
> > > cd debian/tmp/test-working-directory && pypy -m pytest --lsof -rfsxX
> > > --ignore=/<>/testing/freeze
> > > --ignore=/<>/testing/test_entry_points.py
> > > --ignore=/<>/testing/test_pdb.py /<>/testing
> > > dh_auto_test: pybuild --test -i pypy -p 5.6 --system=custom
> > > --test-args=cd debian/tmp/test-working-directory && {interpreter} -m
> > > pytest --lsof -rfsxX --ignore={dir}/testing/freeze
> > > --ignore={dir}/testing/test_entry_points.py
> > > --ignore={dir}/testing/test_pdb.py {dir}/testing returned exit code 13
> > > debian/rules:20: recipe for target 'override_dh_auto_test' failed
>
> I'm unable to reproduce the crash. Could you please provide a backtrace?
Can you provide a build log and diff it with mine?
Lucas
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#860673: Bug#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity
Chris Lamb writes: > Lucas Nussbaum wrote: > >> > test_output_verbose (test_runner.test_debug_sql.TestDebugSQL) ... ok >> > E: Build killed with signal TERM after 150 minutes of inactivity > > Can't reproduce this locally alas... I couldn't reproduce this locally. I use a 32bit schroot. -- Brian May ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#860663: Bug#860663: pytest: FTBFS on i386: segfault during tests
Control: tags -1 + moreinfo unreproducible
On 2017-04-19 09:26:48, Lucas Nussbaum wrote:
> Source: pytest
> Version: 3.0.6-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
> Justification: FTBFS in stretch on i386
>
> Hi,
>
> During a rebuild of all packages in stretch (in a stretch chroot, not a
> sid chroot), your package failed to build on i386.
>
> Relevant part (hopefully):
> > ../../../testing/test_pluginmanager.py ...
> > ../../../testing/test_pytester.py x...
> > ../../../testing/test_recwarn.py ..
> > ../../../testing/test_resultlog.py ...
> > ../../../testing/test_runner.py
> > ...sss.....x...
> > ../../../testing/test_runner_xunit.py ...
> > ../../../testing/test_session.py .
> > ../../../testing/test_skipping.py
> > ..x..
> > ../../../testing/test_terminal.py
> > ..s..s.
> > ../../../testing/test_tmpdir.py ...s
> > ../../../testing/test_unittest.py
> >
> > ../../../testing/code/test_code.py ..
> > ../../../testing/code/test_excinfo.py Segmentation fault
> > E: pybuild pybuild:283: test: plugin custom failed with: exit code=139: cd
> > debian/tmp/test-working-directory && pypy -m pytest --lsof -rfsxX
> > --ignore=/<>/testing/freeze
> > --ignore=/<>/testing/test_entry_points.py
> > --ignore=/<>/testing/test_pdb.py /<>/testing
> > dh_auto_test: pybuild --test -i pypy -p 5.6 --system=custom --test-args=cd
> > debian/tmp/test-working-directory && {interpreter} -m pytest --lsof -rfsxX
> > --ignore={dir}/testing/freeze --ignore={dir}/testing/test_entry_points.py
> > --ignore={dir}/testing/test_pdb.py {dir}/testing returned exit code 13
> > debian/rules:20: recipe for target 'override_dh_auto_test' failed
I'm unable to reproduce the crash. Could you please provide a backtrace?
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Processed: Re: Bug#860663: pytest: FTBFS on i386: segfault during tests
Processing control commands: > tags -1 + moreinfo unreproducible Bug #860663 [src:pytest] pytest: FTBFS on i386: segfault during tests Added tag(s) unreproducible and moreinfo. -- 860663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] python-rpaths_0.13-1_amd64.changes ACCEPTED into unstable, unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 18 Apr 2017 11:31:21 +0100 Source: python-rpaths Binary: python3-rpaths python-rpaths-doc Architecture: source all Version: 0.13-1 Distribution: unstable Urgency: low Maintainer: Debian Python Modules Team Changed-By: Ghislain Antony Vaillant Description: python-rpaths-doc - documentation for rpaths python3-rpaths - cross-platform path manipulation library for Python Closes: 860529 Changes: python-rpaths (0.13-1) unstable; urgency=low . * Initial release. (Closes: #860529) Checksums-Sha1: 294d4b641a8002076b21615fae5fd0e88bf5a6ed 2276 python-rpaths_0.13-1.dsc ffd23fbd48bf5aeeb6253620eadd402221763377 25401 python-rpaths_0.13.orig.tar.gz 2358076e136390ba1403be1c4cc4a4e00c5c91ca 2980 python-rpaths_0.13-1.debian.tar.xz e4a9b5461cfb3c43ea38acd036bfefe75e5c9e7a 25470 python-rpaths-doc_0.13-1_all.deb fda44025f84feee993616bbc3560ca9a9d0cb998 5938 python-rpaths_0.13-1_amd64.buildinfo bb3448d241fe278aaabc3175f91a94b0007e7b4d 13972 python3-rpaths_0.13-1_all.deb Checksums-Sha256: c3f492e4d31c6ecf6dd296e19840a34f66294cb8f66325318b34248338a199c2 2276 python-rpaths_0.13-1.dsc fdb548e6bacc451b6f929d888cc1e79e8f94abae938c5bd69ac367f5c2f95a1c 25401 python-rpaths_0.13.orig.tar.gz 33f7bfb3ccd41f4422973cacc0b82e90bc89f91002978e4c6779e54e2495776e 2980 python-rpaths_0.13-1.debian.tar.xz 1235bbb55ce1db321daab9180515c785faed9ca7d9e7611810bf8c7fd893042d 25470 python-rpaths-doc_0.13-1_all.deb c1c8bd35cbc02aff85ba96db6a5f41b1308da3aa734c723613136879f986ca74 5938 python-rpaths_0.13-1_amd64.buildinfo 0cc0b4f74fa9561cf72493667a4a1dd7b55a88d22e81b2b17b2ae6428de1728e 13972 python3-rpaths_0.13-1_all.deb Files: c5f165a0b607f1589ecbc142a8fb6471 2276 python optional python-rpaths_0.13-1.dsc 4da06091dee244b92b7f8a5c5a84a4c8 25401 python optional python-rpaths_0.13.orig.tar.gz 1cce3a6baf84bcb5f76a8f8e4e7d8ab2 2980 python optional python-rpaths_0.13-1.debian.tar.xz 5a525ffe126b7ac617ae0ec9b8a6cdcd 25470 doc optional python-rpaths-doc_0.13-1_all.deb dad6423c1da9ab34da1cf80e5da23d06 5938 python optional python-rpaths_0.13-1_amd64.buildinfo 571d80c430cb7b8f92196e402a1aae27 13972 python optional python3-rpaths_0.13-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJY9y6wAAoJEFeKBJTRxkbRl70QAJV0kbmA/RxatEWiyndPJQJ7 jgJoYVxzdrOfTSP51hXiRNtsd5ygAx4mfhoSkMEDPImLTqZSk16nOoyUHqUuBJMc 6cdgz80oHn6NlXtGzLHhvCf2dbNpmKl455tHjfURXYqMah9WMmX083z2zdB827f2 HtV6gHnzk4f87fzdtG+tgyHVijBJqmDmDLk9bWXumu0qwc6eVNi2OnJDanTj8zj6 QApu9XLn5hWPUvII1pS0LRzJ5TDhHVc9EDM0nnifzsqdgtOmabAuBqxEPf0UXaT2 BgqZH32yM0tjwCRl3HUZCoinChfCRdSE61mxe3TMo2pkQwE9KQ3Lh4SojcZ3G+Ne YfCQEVEv6CxQBMLBVECJWla7Ccq8I7nvscwDvcah9t/qJO0wM0AHI32eHmtKU6oE xe5nwJ3Q6mVaY2r8/VCJgiwqSzGZ3wDZ0HqKxxycxmraTuga4gXVfeKRlONLA6Md 9UhydB5TiWdrYgR8ranEVinqp1ya7kEg/4OY2b6hS34K1azRhhZKc4gYdAnz+vFn ootXvWHY/rpJ6n997CHgB0Ojcu/nrZEhZxd5Lqm04fpjIJ9Ge4MvIVctV8XhvMDW PpvJ8wsIyLRUgzkfISsWOhYxMJX5ghm+W5xWX2TvjjebFpeh3PplEOJQ75kGv4/E Lwa4y25zBrl9o9xR/xAB =soAG -END PGP SIGNATURE- Thank you for your contribution to Debian. ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity
On 19/04/17 at 16:18 +0100, Chris Lamb wrote: > Lucas Nussbaum wrote: > > > That's a build log for amd64, not i386. > > D'oh! > > > python2.7[39117]: segfault at ffc2cffc ip f61a8170 sp > > ffc2d000 error 6 in libsqlite3.so.0.8.6[f6135000+115000] > > I don't have stretch/i386 within reach atm but this looks like it has > narrowed it down. Any chance of getting a backtrace with symbols? (Interestingly, when restricting the testsuite to the relevant module, it doesn't segfault) Here is the backtrace: Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". Core was generated by `python2.7 ./runtests.py --verbosity=2 --parallel 1 --failfast'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0xf61c70f0 in sqlite3Select (pParse=pParse@entry=0xff954300, p=p@entry=0xfee8ed60, pDest=pDest@entry=0xff91e124) at sqlite3.c:120376 120376 sqlite3.c: No such file or directory. #0 0xf61c70f0 in sqlite3Select (pParse=pParse@entry=0xff954300, p=p@entry=0xfee8ed60, pDest=pDest@entry=0xff91e124) at sqlite3.c:120376 #1 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, p=p@entry=0xfe9c0dc0, pDest=pDest@entry=0xff91e314) at sqlite3.c:117808 #2 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, p=p@entry=0xfe9c0dc0, pDest=pDest@entry=0xff91e314) at sqlite3.c:120465 #3 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, p=p@entry=0xfea6d498, pDest=pDest@entry=0xff91e504) at sqlite3.c:117808 #4 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, p=p@entry=0xfea6d498, pDest=pDest@entry=0xff91e504) at sqlite3.c:120465 #5 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, p=p@entry=0xfed837c8, pDest=pDest@entry=0xff91e6f4) at sqlite3.c:117808 #6 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, p=p@entry=0xfed837c8, pDest=pDest@entry=0xff91e6f4) at sqlite3.c:120465 #7 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, p=p@entry=0xff10c728, pDest=pDest@entry=0xff91e8e4) at sqlite3.c:117808 #8 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, p=p@entry=0xff10c728, pDest=pDest@entry=0xff91e8e4) at sqlite3.c:120465 #9 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, p=p@entry=0xfb40d7a8, pDest=pDest@entry=0xff91ead4) at sqlite3.c:117808 #10 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, p=p@entry=0xfb40d7a8, pDest=pDest@entry=0xff91ead4) at sqlite3.c:120465 #11 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, p=p@entry=0xf9caeb60, pDest=pDest@entry=0xff91ecc4) at sqlite3.c:117808 #12 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, p=p@entry=0xf9caeb60, pDest=pDest@entry=0xff91ecc4) at sqlite3.c:120465 #13 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, p=p@entry=0xff183400, pDest=pDest@entry=0xff91eeb4) at sqlite3.c:117808 #14 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, p=p@entry=0xff183400, pDest=pDest@entry=0xff91eeb4) at sqlite3.c:120465 #15 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, p=p@entry=0xf9c57408, pDest=pDest@entry=0xff91f0a4) at sqlite3.c:117808 #16 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, p=p@entry=0xf9c57408, pDest=pDest@entry=0xff91f0a4) at sqlite3.c:120465 #17 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, p=p@entry=0xf9ca9488, pDest=pDest@entry=0xff91f294) at sqlite3.c:117808 #18 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, p=p@entry=0xf9ca9488, pDest=pDest@entry=0xff91f294) at sqlite3.c:120465 #19 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, p=p@entry=0xfbc66de0, pDest=pDest@entry=0xff91f484) at sqlite3.c:117808 #20 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, p=p@entry=0xfbc66de0, pDest=pDest@entry=0xff91f484) at sqlite3.c:120465 #21 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, p=p@entry=0xff0763a8, pDest=pDest@entry=0xff91f674) at sqlite3.c:117808 #22 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, p=p@entry=0xff0763a8, pDest=pDest@entry=0xff91f674) at sqlite3.c:120465 #23 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, p=p@entry=0xfead0a80, pDest=pDest@entry=0xff91f864) at sqlite3.c:117808 #24 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, p=p@entry=0xfead0a80, pDest=pDest@entry=0xff91f864) at sqlite3.c:120465 #25 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, p=p@entry=0xff0878a0, pDest=pDest@entry=0xff91fa54) at sqlite3.c:117808 #26 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, p=p@entry=0xff0878a0, pDest=pDest@entry=0xff91fa54) at sqlite3.c:120465 #27 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, p=p@entry=0xee765630, pDest=pDest@entry=0xff91fc44) at sqlite3.c:117808 #28 0xf61c7731 in sqlite3Select (pParse=pParse@entry=0xff954300, p=p@entry=0xee765630, pDest=pDest@entry=0xff91fc44) at sqlite3.c:120465 #29 0xf61d1f4a in multiSelect (pParse=pParse@entry=0xff954300, p=p@entry=0xfee37768, pDest
[Python-modules-team] Bug#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity
Lucas Nussbaum wrote: > That's a build log for amd64, not i386. D'oh! > python2.7[39117]: segfault at ffc2cffc ip f61a8170 sp > ffc2d000 error 6 in libsqlite3.so.0.8.6[f6135000+115000] I don't have stretch/i386 within reach atm but this looks like it has narrowed it down. Any chance of getting a backtrace with symbols? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity
On 19/04/17 at 15:59 +0100, Chris Lamb wrote: > Hi Lucas, > > > I tried again and still can; maybe diff your build log with mine to see > > if something comes up? > > Good idea; mine is at: > > https://gist.github.com/lamby/e2152b47a6d3d69d29e34975059c6be7/raw That's a build log for amd64, not i386. > (Testsuite runs in parallel so this might be difficult...) Indeed. However, the test suite also fails when run manually, with python2.7 ./runtests.py --verbosity=2 --parallel 1 --failfast I get: test_can_defer_constraint_checks (delete.tests.DeletionTests) ... skipped "Database doesn't support feature(s): can_defer_constraint_checks" test_cannot_defer_constraint_checks (delete.tests.DeletionTests) ... ok test_delete_with_keeping_parents (delete.tests.DeletionTests) ... ok test_delete_with_keeping_parents_relationships (delete.tests.DeletionTests) ... ok test_deletion_order (delete.tests.DeletionTests) ... ok test_hidden_related (delete.tests.DeletionTests) ... ok test_instance_update (delete.tests.DeletionTests) ... ok test_large_delete (delete.tests.DeletionTests) ... Segmentation fault dmesg shows: python2.7[39117]: segfault at ffc2cffc ip f61a8170 sp ffc2d000 error 6 in libsqlite3.so.0.8.6[f6135000+115000] Lucas ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity
Hi Lucas, > I tried again and still can; maybe diff your build log with mine to see > if something comes up? Good idea; mine is at: https://gist.github.com/lamby/e2152b47a6d3d69d29e34975059c6be7/raw (Testsuite runs in parallel so this might be difficult...) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity
Hi! On 19/04/17 at 14:02 +0100, Chris Lamb wrote: > Lucas Nussbaum wrote: > > > > test_output_verbose (test_runner.test_debug_sql.TestDebugSQL) ... ok > > > E: Build killed with signal TERM after 150 minutes of inactivity > > Can't reproduce this locally alas... I tried again and still can; maybe diff your build log with mine to see if something comes up? Lucas ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity
Lucas Nussbaum wrote: > > test_output_verbose (test_runner.test_debug_sql.TestDebugSQL) ... ok > > E: Build killed with signal TERM after 150 minutes of inactivity Can't reproduce this locally alas... Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] python-rpaths_0.13-1_amd64.changes is NEW
binary:python-rpaths-doc is NEW. binary:python3-rpaths is NEW. binary:python-rpaths-doc is NEW. binary:python3-rpaths is NEW. source:python-rpaths is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Processing of python-rpaths_0.13-1_amd64.changes
python-rpaths_0.13-1_amd64.changes uploaded successfully to localhost along with the files: python-rpaths_0.13-1.dsc python-rpaths_0.13.orig.tar.gz python-rpaths_0.13-1.debian.tar.xz python-rpaths-doc_0.13-1_all.deb python-rpaths_0.13-1_amd64.buildinfo python3-rpaths_0.13-1_all.deb Greetings, Your Debian queue daemon (running on host usper.debian.org) ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Processing of python-rpaths_0.13-1_amd64.changes
python-rpaths_0.13-1.dsc has incorrect size; deleting it python-rpaths_0.13-1.debian.tar.xz has incorrect size; deleting it Greetings, Your Debian queue daemon (running on host usper.debian.org) ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#860619: Bug#860619: python-passlib: FTBFS on i386: Test failures
Brian May writes: > I believe this is fixed in version 1.7.1 which is in unstable. Unblock request sent: #860717 -- Brian May ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#860619: Bug#860619: python-passlib: FTBFS on i386: Test failures
Lucas Nussbaum writes: > Relevant part (hopefully): >> File "", line 673, in _load_unlocked >> File "", line 673, in exec_module >> File "", line 222, in >> _call_with_frames_removed >> File "/<>/passlib/tests/test_totp.py", line 61, in >> datetime.datetime.utcfromtimestamp(max_time_t << 1) >> OverflowError: timestamp out of range for platform time_t I believe this is fixed in version 1.7.1 which is in unstable. This is actually Python 3.6 bug: https://bugs.python.org/issue29100 https://bugs.python.org/issue29346 python-passlib applied a work around: https://bitbucket.org/ecollins/passlib/commits/80f838f5771f6753b0e46716ab25b48641aeef89 -- Brian May ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#860619: Bug#860619: python-passlib: FTBFS on i386: Test failures
Brian May writes: > This is actually Python 3.6 bug: Actually that claim makes no sense as Python 3.6 isn't in Debian testing or unstable yet. -- Brian May ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#860668: sorl-thumbnail: FTBFS on i386: segfault during tests
Source: sorl-thumbnail Version: 12.3+git20160928-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): > tests/thumbnail_tests/test_filters.py > tests/thumbnail_tests/test_kvstore.py . > tests/thumbnail_tests/test_parsers.py . > tests/thumbnail_tests/test_storage.py > tests/thumbnail_tests/test_templatetags.py ss. > > === 63 passed, 3 skipped, 2 xfailed in 5.14 seconds > > = test session starts > == > platform linux2 -- Python 2.7.13, pytest-3.0.6, py-1.4.32, pluggy-0.4.0 > django settings: tests.settings.wand (from environment variable) > rootdir: /<>/sorl-thumbnail-12.3+git20160928, inifile: tox.ini > plugins: django-2.9.1 > collected 68 items > > tests/thumbnail_tests/test_alternative_resolutions.py Segmentation fault > debian/rules:22: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/2017/04/18/sorl-thumbnail_12.3+git20160928-1_testing-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. ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity
Source: python-django Version: 1:1.10.7-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): > Ensure is_null is handled correctly. ... ok > test_limited_filter (admin_views.tests.AdminViewBasicTest) > Ensure admin changelist filters do not contain objects excluded via > limit_choices_to. ... ok > test_logout_and_password_change_URLs (admin_views.tests.AdminViewBasicTest) > ... ok > test_multiple_sort_same_field (admin_views.tests.AdminViewBasicTest) ... ok > test_named_group_field_choices_change_list > (admin_views.tests.AdminViewBasicTest) ... ok > test_named_group_field_choices_filter (admin_views.tests.AdminViewBasicTest) > ... ok > test_popup_add_POST (admin_views.tests.AdminViewBasicTest) ... ok > test_popup_dismiss_related (admin_views.tests.AdminViewBasicTest) ... ok > test_relation_spanning_filters (admin_views.tests.AdminViewBasicTest) ... ok > test_resolve_admin_views (admin_views.tests.AdminViewBasicTest) ... ok > test_sort_indicators_admin_order (admin_views.tests.AdminViewBasicTest) ... ok > test_trailing_slash_required (admin_views.tests.AdminViewBasicTest) ... ok > test_output_normal (test_runner.test_debug_sql.TestDebugSQL) ... ok > test_output_verbose (test_runner.test_debug_sql.TestDebugSQL) ... ok > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://aws-logs.debian.net/2017/04/18/python-django_1.10.7-1_testing-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. ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#860663: pytest: FTBFS on i386: segfault during tests
Source: pytest
Version: 3.0.6-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386
Hi,
During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.
Relevant part (hopefully):
> ../../../testing/test_pluginmanager.py ...
> ../../../testing/test_pytester.py x...
> ../../../testing/test_recwarn.py ..
> ../../../testing/test_resultlog.py ...
> ../../../testing/test_runner.py
> ...sss.....x...
> ../../../testing/test_runner_xunit.py ...
> ../../../testing/test_session.py .
> ../../../testing/test_skipping.py
> ..x..
> ../../../testing/test_terminal.py
> ..s..s.
> ../../../testing/test_tmpdir.py ...s
> ../../../testing/test_unittest.py
> ../../../testing/code/test_code.py ..
> ../../../testing/code/test_excinfo.py Segmentation fault
> E: pybuild pybuild:283: test: plugin custom failed with: exit code=139: cd
> debian/tmp/test-working-directory && pypy -m pytest --lsof -rfsxX
> --ignore=/<>/testing/freeze
> --ignore=/<>/testing/test_entry_points.py
> --ignore=/<>/testing/test_pdb.py /<>/testing
> dh_auto_test: pybuild --test -i pypy -p 5.6 --system=custom --test-args=cd
> debian/tmp/test-working-directory && {interpreter} -m pytest --lsof -rfsxX
> --ignore={dir}/testing/freeze --ignore={dir}/testing/test_entry_points.py
> --ignore={dir}/testing/test_pdb.py {dir}/testing returned exit code 13
> debian/rules:20: recipe for target 'override_dh_auto_test' failed
The full build log is available from:
http://aws-logs.debian.net/2017/04/18/pytest_3.0.6-1_testing-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.
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#860656: python-biplist: FTBFS on i386: dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned exit code 13
Source: python-biplist
Version: 1.0.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386
Hi,
During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.
Relevant part (hopefully):
> debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config
> running config
> I: pybuild base:184: python3.5 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/biplist
> copying biplist/__init__.py ->
> /<>/.pybuild/pythonX.Y_2.7/build/biplist
> running egg_info
> writing biplist.egg-info/PKG-INFO
> writing top-level names to biplist.egg-info/top_level.txt
> writing dependency_links to biplist.egg-info/dependency_links.txt
> reading manifest file 'biplist.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'biplist.egg-info/SOURCES.txt'
> I: pybuild base:184: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.5/build/biplist
> copying biplist/__init__.py ->
> /<>/.pybuild/pythonX.Y_3.5/build/biplist
> running egg_info
> writing dependency_links to biplist.egg-info/dependency_links.txt
> writing biplist.egg-info/PKG-INFO
> writing top-level names to biplist.egg-info/top_level.txt
> reading manifest file 'biplist.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'biplist.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build;
> python2.7 -m nose tests
> .F...
> ==
> FAIL: testIntBoundaries (test_write.TestWritePlist)
> --
> Traceback (most recent call last):
> File "/<>/.pybuild/pythonX.Y_2.7/build/tests/test_write.py",
> line 272, in testIntBoundaries
> self.roundTrip(cases)
> File "/<>/.pybuild/pythonX.Y_2.7/build/tests/test_write.py",
> line 41, in roundTrip
> self.assertEqual(repr(case if expected is None else expected),
> repr(readResult))
> AssertionError: '[4294967295L, 4294967294L, 4294967296L, 4294967293L,
> 4294967297L, 8589934590L, 2147483647L]' != '[4294967295L, 4294967294L,
> 4294967296L, 4294967293L, 4294967297L, 8589934590L, 2147483647]'
>
> --
> Ran 41 tests in 0.128s
>
> FAILED (failures=1)
> E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd
> /<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose tests
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned
> exit code 13
The full build log is available from:
http://aws-logs.debian.net/2017/04/18/python-biplist_1.0.1-1_testing-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.
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#860619: python-passlib: FTBFS on i386: Test failures
Source: python-passlib
Version: 1.7.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386
Hi,
During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.
Relevant part (hopefully):
> File "", line 673, in _load_unlocked
> File "", line 673, in exec_module
> File "", line 222, in _call_with_frames_removed
> File "/<>/passlib/tests/test_totp.py", line 61, in
> datetime.datetime.utcfromtimestamp(max_time_t << 1)
> OverflowError: timestamp out of range for platform time_t
>
> --
> Ran 2810 tests in 217.655s
>
> FAILED (errors=1, skipped=1191)
> Test failed:
> error: Test failed: failures=0>
> E: pybuild pybuild:283: test: plugin custom failed with: exit code=1:
> python3.5 setup.py test
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.5
> --system=custom --test-args={interpreter} setup.py test returned exit code 13
> debian/rules:9: recipe for target 'override_dh_auto_test' failed
The full build log is available from:
http://aws-logs.debian.net/2017/04/18/python-passlib_1.7.0-1_testing-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.
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
