[issue10418] test_io hangs on 3.1.3rc1

Virgil Dupras added the comment: Ooh, darn, that was it. I installed it and afterwards, the tests passed. Sorry for the fuss, I'll keep that gotcha in mind next time. -- resolution: -> invalid status: open -> closed ___ Python tracker

[issue10418] test_io hangs on 3.1.3rc1

Ned Deily added the comment: Be careful when running a framework build from the build directory without installing it. Chances are you are actually dynamically linking to an older existing framework in /Library/Frameworks. (Try looking at sys.modules to see what I mean.) You'll either need

[issue10418] test_io hangs on 3.1.3rc1

R. David Murray added the comment: Ronald hasn't replied yet and he's the most likely to be in a position to try to reproduce it. Even if you can't fix it, figuring out more about how that individual test is arriving at the hang could be useful. If you've got the chops to look at the hang i

[issue10418] test_io hangs on 3.1.3rc1

Virgil Dupras added the comment: Nobody else can reproduce the bug? I'm not sure I can fix this (although I can try). I tried to re-compile 3.1.2 with the same flags and run test_io and it passes, so something happened between 3.1.2 and 3.1.3rc1. So, I'll give it a look, but if someone more

[issue10418] test_io hangs on 3.1.3rc1

Antoine Pitrou added the comment: > I ran the test with the -v option flag. The malloc error don't happen > at the same place the hang up happens. The first one happens at: The malloc error is normal, then, it's part of that test. It's a pity OS X dumps something on stderr, though. > And final

[issue10418] test_io hangs on 3.1.3rc1

Virgil Dupras added the comment: I ran the test with the -v option flag. The malloc error don't happen at the same place the hang up happens. The first one happens at: test_readline (test.test_io.PyIOTest) ... ok test_unbounded_file (test.test_io.PyIOTest) ... skipped 'test can only run in a

[issue10418] test_io hangs on 3.1.3rc1

Antoine Pitrou added the comment: Can you run regrtest with the -v option, to know which test case fails? (we have several OS X buildbots which run this test fine, by the way, including a Snow Leopard instance) Note: 9223372036854775808 is 2**63 or 0x8000. -- nosy: +ronal

[issue10418] test_io hangs on 3.1.3rc1

Changes by R. David Murray : -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue10418] test_io hangs on 3.1.3rc1

New submission from Virgil Dupras : I downloaded Python 3.1.3rc1 this morning to do my civic duty of testing it. I don't know what I'm doing wrong, but for me, test_io hangs and never completed. I'm on OS X 10.6.5. I ran it with: $ ./python.exe Lib/test/regrtest.py test_io And I got: test_io