STINNER Victor <vstin...@python.org> added the comment:
> I tested with both PR 19312 and PR 19308 and I still have the same crash
Which test is causing the issue? Does it still crash if you comment
test_input_no_stdout_fileno()? Try to rename it "Xtest_input_no_stdout_fileno"
to skip it.
What if you only run this test?
./python -m test test_builtin -m test_input_no_stdout_fileno -F -j10 -v
Maybe this test should register a signal handler for SIGHUP?
This bug looks like bpo-38547 which affected test_pty. I fixed it by
registering a SIGHUP signal handler:
commit a1838ec2592e5082c75c77888f2a7a3eb21133e5
Author: Victor Stinner <vstin...@python.org>
Date: Mon Dec 9 11:57:05 2019 +0100
bpo-38547: Fix test_pty if the process is the session leader (GH-17519)
Fix test_pty: if the process is the session leader, closing the
master file descriptor raises a SIGHUP signal: simply ignore SIGHUP
when running the tests.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue40140>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
