On 3/30/06, Tim Peters <[EMAIL PROTECTED]> wrote:
> Disabling a test on a platform is usually a bad thing, overall. The
Agreed.
> purpose of the test suite isn't to get a lot of green buildbot boxes
> <0.5 wink>, it's to determine whether Python works as expected. If a
> platform bug causes so
Disabling a test on a platform is usually a bad thing, overall. The
purpose of the test suite isn't to get a lot of green buildbot boxes
<0.5 wink>, it's to determine whether Python works as expected. If a
platform bug causes some test to fail, then that test _should_ fail on
that platform -- it
Neal Norwitz wrote:
> These issues are on HEAD. There might be some others I missed.
>
> With cc there are at least 2 issues:
> * test_file causes interpreter exit due to sys.stdin.seek(-1)
> * test_pty fails apparently due to whitespace differences
>
> http://www.python.org/dev/buildbot/all/a
Neal Norwitz wrote:
> The question is how to fix these. test_float and test_struct fail due
> to a Floating Point Exception signal (SIGFPE).
I would hope that there is some way to control the floating point error
mode of the CPU (*). Changing it would be one option; Tim hopefully can
tell us whet
These issues are on HEAD. There might be some others I missed.
With cc there are at least 2 issues:
* test_file causes interpreter exit due to sys.stdin.seek(-1)
* test_pty fails apparently due to whitespace differences
http://www.python.org/dev/buildbot/all/alpha%20Tru64%205.1%20trunk/builds/
