Your message dated Fri, 21 Apr 2017 11:22:02 +0200
with message-id <[email protected]>
and subject line Re: Bug#860663: [Python-modules-team] Bug#860663: pytest:
FTBFS on i386: segfault during tests
has caused the Debian Bug report #860663,
regarding pytest: FTBFS on i386: segfault during tests
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.)
--
860663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860663
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pytest
Version: 3.0.6-1
Severity: serious
Tags: stretch sid
User: [email protected]
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
> ...................sssssss...ssss......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 ....................ssssssss................
> ../../../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=/<<PKGBUILDDIR>>/testing/freeze
> --ignore=/<<PKGBUILDDIR>>/testing/test_entry_points.py
> --ignore=/<<PKGBUILDDIR>>/testing/test_pdb.py /<<PKGBUILDDIR>>/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.
--- End Message ---
--- Begin Message ---
On 20/04/17 at 10:38 +0200, Lucas Nussbaum wrote:
> On 20/04/17 at 09:40 +0200, Sebastian Ramacher wrote:
> > > I've generated a core file and put it at:
> > > http://aws-logs.debian.net/2017/04/18/pypy-segfault.core.gz
> >
> > Thanks, but it fails with 403.
>
> Fixed, sorry
>
> > Currently my best explanation is that pypy
> > crashes during pytest's excinfo tests when running with a jessie kernel,
> > but not
> > with a stretch kernel.
>
> Yes, I checked, and upgrading the kernel to stretch's fixes
> the problem. Interesting.
Hi,
I did the archive rebuild that resulted in this bug on a machine with a
jessie kernel. I did another rebuild on a machine with a stretch
kernel, and this failure disappeared.
My best guess is that this has something to do with a stack overflow,
in a way similar to #750593 (see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750593#157 and #797530
(fixed in stretch, not jessie).
Given that this doesn't affect building on a machine with a stretch
kernel, I'm closing the bug.
Lucas
--- End Message ---
