[New-bugs-announce] [issue4970] test_os causes delayed failure on x86 gentoo buildbot: Unknown signal 32
report at bugs.python.org
Sat Jan 17 12:09:45 CET 2009
New submission from Mark Dickinson <dickinsm at gmail.com>:
The x86 gentoo 3.0 and 3.x buildbots have been failing for a while at the test stage, with:
make: *** [buildbottest] Unknown signal 32
program finished with exit code 2
I noticed a common denominator with these failures, which is that they always seem to occur a few tests after
test_os has been run. So it looks as though something in test_os is causing this.
Can anyone reproduce this (I can't on any of the machines I have access to), and (e.g., by trial and error) identify
which of the test_os tests is causing this?
title: test_os causes delayed failure on x86 gentoo buildbot: Unknown signal 32
versions: Python 3.0, Python 3.1
Python tracker <report at bugs.python.org>
More information about the New-bugs-announce