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

Groups > linux.debian.maint.python > #12287 > unrolled thread

pytest and core dump

Back to article view | Back to linux.debian.maint.python

Contents

  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

#12287 — pytest and core dump

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.
It should help the debuging.

thanks for your help


Frederic


[1] https://salsa.debian.org/science-team/vitables/-/jobs/554052

[toc] | [next] | [standalone]

#12289

[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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web