Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #12289

Re: pytest and core dump

From Dmitry Shachnev <mitya57@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: pytest and core dump
Date 2020-02-09 21:00 +0100
Message-ID <zy0Uh-2lV-5@gated-at.bofh.it> (permalink)
References <zxX0m-8uS-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Hi,

On Sun, Feb 09, 2020 at 03:31:39PM +0000, PICCA Frederic-Emmanuel wrote:
> Hello, I am working on the vitables package.
>
> during the build I get this error message [1]
>
> ============================= test session starts ==============================
> 1567 platform linux -- Python 3.7.6, pytest-4.6.9, py-1.8.1, pluggy-0.13.0
> 1568 rootdir: /builds/science-team/vitables/debian/output/vitables-3.0.2
> 1569 collected 54 items
> 1570 tests/test_filenode.py Aborted (core dumped)
> 1571 E: pybuild pybuild:341: test: plugin distutils failed with: e
>
> This core dump is generated in the salsa-ci runners.
>
> I would like a backtrace of this core dump.
>
> so my question is how can we instrument the d/rules in order to print a
> stack trace during the build in case of core dump.

To get the Python traceback, you can export PYTHONFAULTHANDLER=1.

To get the C stack trace, you need to run the Python interpreter in a debugger
like gdb. Better to do this locally of course, not in the CI.

--
Dmitry Shachnev

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

pytest and core dump PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2020-02-09 16:50 +0100
  Re: pytest and core dump Dmitry Shachnev <mitya57@debian.org> - 2020-02-09 21:00 +0100

csiph-web