You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
test_subprocess creates a core dump on FreeBSD #74633
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2017-06-30.23:41:31.481>created_at=<Date2017-05-24.00:24:03.414>labels= ['3.7', 'tests']
title='test_subprocess creates a core dump on FreeBSD'updated_at=<Date2017-06-30.23:41:31.477>user='https://github.com/vstinner'
I'm surprised that we only detect hard crashes only indirectly through the
creation of core dump files... Some tests might be enhanced to raise an
exception at least if the process was killed by a signal, maybe also if the
exit code is non-zero (depending on the test).
We had a similar but different issue in test_io which created a core dump
on a deliberate crash.
Activity
vstinner commentedon May 24, 2017
Eric Snow: do you think that it could be related to your recent subinterpreter changes please?
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%20CURRENT%20Debug%203.x/builds/311/steps/test/logs/stdio
0:08:26 load avg: 3.35 [253/405] test_subprocess failed (env changed) (98 sec) -- running: test_io (30 sec)
Warning -- files was modified by test_subprocess
Before: []
After: ['python.core']
ericsnowcurrently commentedon May 24, 2017
That looks similar to other failures due to an issue fixed in a later PR. It shouldn't be an issue any longer. I'll double check in the morning.
vstinner commentedon May 24, 2017
I'm surprised that we only detect hard crashes only indirectly through the
creation of core dump files... Some tests might be enhanced to raise an
exception at least if the process was killed by a signal, maybe also if the
exit code is non-zero (depending on the test).
We had a similar but different issue in test_io which created a core dump
on a deliberate crash.
ericsnowcurrently commentedon May 25, 2017
At this point I'm not convinced the failure is due to my recent changes. Regardless, I do agree with you about detecting hard crashes.
vstinner commentedon May 31, 2017
Sadly, I'm unable to reproduce the issue on my FreeBSD 11 VM :-(
vstinner commentedon Jun 26, 2017
Oops, I mentioned the wrong bpo in my PRs: the fix was pushed using bpo-30764 identifier :-/
vstinner commentedon Jun 27, 2017
It seems like test_child_terminated_in_stopped_state() of test_subprocess on Python 2.7 fails on some macOS versions, see:
http://bugs.python.org/issue30764#msg296966
Can someone please try to reproduce the bug? I'm unable to reproduce the bug on Darwin 16.5.0 (macOS Sierra?).
vstinner commentedon Jun 30, 2017
New changeset fd93f37 by Victor Stinner in branch '2.7':
bpo-30448: Fix support.SuppressCrashReport on macOS (bpo-2515)
fd93f37
vstinner commentedon Jun 30, 2017
macOS 2.7 buildbots are back. All known bugs are fixed, I close the issue.