[Python-modules-team] Bug#800392: Bug#800392: Bug#800392: python-numpy: FTBFS on powerpc due to test failure

[Julian Taylor]

On 30.09.2015 01:01, Sandro Tosi wrote:
> On Tue, Sep 29, 2015 at 8:05 AM, Julian Taylor
> <jtaylor.debian at googlemail.com> wrote:
>> On 28.09.2015 20:58, Scott Kitterman wrote:
>>>
>>> Seems like this may be related to #702169.
>>>
>>
>> no, powerpc is the arch with the broken malloc:
>> https://sourceware.org/bugzilla/show_bug.cgi?id=6527
>>
>> the test should probably just be ignored (as it has been in the past) it
>> has always been broken and nobody ever cared.
> 
> Is there an elegant way to instruct numpy testsuite to just ignore
> errors on powerpc? I would really love to keep the test failures as
> blocking on all Debian archs. I cant think of any smart way to keep
> the 'set -e' for all archs except powerpc
> 
> on way would be to just skip that test (in the last failure it was
> always test_multiarray.TestClip.test_basic) but of course that doesnt
> guarantee that other tests might fail after that (and we dont know
> now) or that other test starts failing (because of the broken malloc
> acting up).
> 

it would probably be best to disable the assert in
lowlevel_strided_loops.c.src on powerpc depending cpp macros, that way
it will also continue to work when users would want to use python-dbg on
ppc if softfaulting is enabled.