New submission from Mark Dickinson <dicki...@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? ---------- messages: 80009 nosy: marketdickinson severity: normal status: open title: test_os causes delayed failure on x86 gentoo buildbot: Unknown signal 32 versions: Python 3.0, Python 3.1 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue4970> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
