Message 80009 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

In-reply-to
Author	mark.dickinson
Recipients	mark.dickinson
Date	2009年01月17日.11:09:44
SpamBayes Score	0.008600475
Marked as misclassified	No
Message-id	<1232190585.86.0.270883273991.issue4970@psf.upfronthosting.co.za>

Content
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?

Content

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?

History
Date	User	Action	Args
2009年01月17日 11:09:45	mark.dickinson	set	recipients: + mark.dickinson
2009年01月17日 11:09:45	mark.dickinson	set	messageid: <1232190585.86.0.270883273991.issue4970@psf.upfronthosting.co.za>
2009年01月17日 11:09:45	mark.dickinson	link	issue4970 messages
2009年01月17日 11:09:44	mark.dickinson	create

homepage