Bug#860673: [Python-modules-team] Bug#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity
On 20/04/17 at 06:54 +1000, Brian May wrote: > Chris Lambwrites: > > > 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. I tried on a smaller EC2 instance (m4.4xlarge, with 16 cores instead of 64) and it did not fail. Lucas
Bug#860673: [Python-modules-team] Bug#860673: python-django: FTBFS on i386: E: Build killed with signal TERM after 150 minutes of inactivity
Chris Lambwrites: > 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
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
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 `-
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 `-
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
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 `-
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.