[issue3862] test_array fails on FreeBSD7 amd64

Georg Brandl added the comment: Closing this old pending issue due to lack of activity. -- nosy: +georg.brandl status: pending -> closed ___ Python tracker ___ ___

[issue3862] test_array fails on FreeBSD7 amd64

Terry J. Reedy added the comment: Was the fix forward ported or is this an issue for 3.1/2? -- nosy: +tjreedy status: open -> pending ___ Python tracker ___ _

[issue3862] test_array fails on FreeBSD7 amd64

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment: Yes, the bleeding obvious became so after some sleep. Committed to trunk as r66708 with the extra fix and a more abbreviated failure message, which I hope is still semantically the same as Mark's suggested text. Will forward port as appr

[issue3862] test_array fails on FreeBSD7 amd64

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > The 2**16 in the error message is wrong. As he says. ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3862] test_array fails on FreeBSD7 amd64

Mark Dickinson <[EMAIL PROTECTED]> added the comment: The 2**16 in the error message is wrong. Maybe the error message should be something like: "Attempt to create array of size larger than maxsize failed to raise MemoryError." A bit verbose, but more accurate. There's another error in that p

[issue3862] test_array fails on FreeBSD7 amd64

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment: On FreeBSD 7.0 amd64, applying Mark's patch does get the test to pass. As noted on python-dev, the response I got from the author of the new malloc() package in FreeBSD 7.x indicates that as of 7.1 the allocator defaults to using sbrk() r

[issue3862] test_array fails on FreeBSD7 amd64

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: The patch looks fine to me, except that the failure message is now out of date. -- nosy: +loewis ___ Python tracker <[EMAIL PROTECTED]> _

[issue3862] test_array fails on FreeBSD7 amd64

Mark Dickinson <[EMAIL PROTECTED]> added the comment: s/Alan/Andrew/. Need more coffee. Apologies. ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3862] test_array fails on FreeBSD7 amd64

Mark Dickinson <[EMAIL PROTECTED]> added the comment: Thanks, Alan. I realised my answer was a shallow one after reading (too late!) the thread you started on python-dev. However, I have a suspicion that that particular array test (test_alloc_overflow) was merely meant to test the code in newar

[issue3862] test_array fails on FreeBSD7 amd64

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment: Mark, your patch will probably get the test to pass, but the underlying reason the test is failing appears to be unexpected behaviour of the platform malloc(). FreeBSD 7.0 introduced a new malloc() implementation that relies on mmap() and

[issue3862] test_array fails on FreeBSD7 amd64

Mark Dickinson <[EMAIL PROTECTED]> added the comment: Does the attached patch help fix this at all? I encountered possibly the same problem on a 64-bit Mac build of Python, and this patch fixed the problem for me. -- keywords: +patch nosy: +marketdickinson Added file: http://bugs.pyth

[issue3862] test_array fails on FreeBSD7 amd64

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment: On FreeBSD 7.0 i386, test_array passes without ulimit -v needing to be set (ie its still the default "unlimited". ___ Python tracker <[EMAIL PROTECTED]> __

[issue3862] test_array fails on FreeBSD7 amd64

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment: I've temporarily got a 7.0 amd64 system running and can confirm what you see. I checked out the 2.5.2 port patches you mentioned, but all the ones that seemed related are already in the 2.6rc1 sources. On a hunch, I used ulimit -v is use

[issue3862] test_array fails on FreeBSD7 amd64

Reed O'Brien <[EMAIL PROTECTED]> added the comment: 2.6rc2 and Python-3.0b3 test_array detail test_alloc_overflow (test.test_array.DoubleTest) ... Killed Fills swap space and dumps core. 2.5.2 test_list test_addmul (test.test_list.ListTest) ... ok test_append (test.test_list.ListTest) ...

[issue3862] test_array fails on FreeBSD7 amd64

Andrew I MacIntyre <[EMAIL PROTECTED]> added the comment: 2.6rc1 test_array passes on FreeBSD 6.3 i386. I don't have a 7.0 box (either i386 or amd64) accessible at the moment to cross check. Can you run the test on its own in verbose mode to get a bit more of an idea where its blowing up? - ie:

[issue3862] test_array fails on FreeBSD7 amd64

New submission from Reed O'Brien <[EMAIL PROTECTED]>: or in FreeBSD? 2.6rc1 and 3.0b3 both fail test_array on FreeBSD7 amd64 test_array passes in 2.5.2 on the same machine but fails test_list the same as test_array... *** Signal 9 -- components: Tests messages: 73204 nosy: robrien sev