[issue4970] test_os causes delayed failure on x86 gentoo buildbot: Unknown signal 32
report at bugs.python.org
Tue Apr 13 17:16:41 CEST 2010
Mark Dickinson <dickinsm at gmail.com> added the comment:
Here's some fairly minimal Python code that produces the signal:
### begin example ###
time.sleep(1.0) # probably irrelevant to the failure
### end example ###
It looks as though the failed os.execv call messes something up internally, so that any attempt thereafter to start a thread produces this signal. I can't see anything obviously wrong with the os.execv implementation (see posix_execv in Modules/posixmodule.c).
There's still the question of what changed between 2.x and 3.x: on 2.x, this buildbot seems perfectly happy.
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list