-
-
Notifications
You must be signed in to change notification settings - Fork 515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
configuration option disabling sucicide on pytest subprocess #1791
Comments
I have never used the trace flag of pytest, so you'd need to tell more about it. Also what suicide are we talking here about, tox vs pytest? |
On Mon, 2021-01-11 at 06:58 +0000, Bernát Gábor wrote:
Tox sends after suicide_timeout the sigint signal to all of its When you call pytest with When you for in detail investigation call pytest with (*) in most cases they just stay unnoticed in the version used to |
This issue was created for 3.x, which is no longer supported, please try with 4.0. |
Thanks I'll do and report. |
Describe what improvement you want and how would this be used. Thanks!
I sometimes need to run pytest under a newer python version eg py38 while my system is running python 3.6 or 3.7 in trace mode
to achieve this i prefer to call it through tox
In tox.ini i have
This basically works as expected but some times the library runs into a endless loop or i want to check if some code executed between two breakpoints is working as expected. This when running pytest directly is achieved by pressing to bail out into pdb debugger. Under tox pytest will be killed after
interrupt_timeout
is elapsed which is annoying in this case. Therefore i would apriciate if there would be a toxno_suicide
ordont_kill
or alike option to tell tox to refrain from sending term signal to its subprocesses or at least pytest if specified as parameter for that option and just pass on SIGINT as SIGINT without killing itself..The text was updated successfully, but these errors were encountered: