octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tests fail on ARM


From: Rik
Subject: Re: Tests fail on ARM
Date: Mon, 23 Dec 2013 11:23:07 -0800

On 12/23/2013 10:59 AM, address@hidden wrote:
> Message: 4
> Date: Mon, 23 Dec 2013 13:35:51 -0500
> From: "John W. Eaton" <address@hidden>
> To: Susi Lehtola <address@hidden>
> Cc: address@hidden
> Subject: Re: Tests fail on ARM
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 12/22/2013 03:51 PM, Susi Lehtola wrote:
>> > On Sun, 22 Dec 2013 11:16:12 +0200
>> > Susi Lehtola <address@hidden> wrote:
>>> >> Looks like there is a problem on the armv7hl architecture
>>> >>
>>> >>    index.tst .............................................. PASS  138/138
>>> >>    io.tst ................................................. PASS   85/85
>>> >>    jit.tst ................................................panic: 
>>> >> Segmentation fault -- stopping myself...
>>> >> make[1]: *** [check] Segmentation fault
>>> >> make[1]: Leaving directory `/builddir/build/BUILD/octave-3.8.0-rc2/test'
>>> >> make: *** [check] Error 2
>>> >> error: Bad exit status from /var/tmp/rpm-tmp.J37nRj (%check)
>>> >>      Bad exit status from /var/tmp/rpm-tmp.J37nRj (%check)
>>> >> RPM build errors:
>>> >> Child return code was: 1
>>> >>
>>> >> Attempted scratch build at
>>> >> http://koji.fedoraproject.org/koji/taskinfo?taskID=6324505
>> >
>> > Does anyone else see this?
> Is jit enabled at compile time?  Run time somehow (it is supposed to be 
> disabled by default).

JIT is disabled at runtime, so it won't get used by ordinary code. 
However, jit.tst is part of the fixed test suite and is specifically for
testing jit so it will turn it on at runtime if possible.

--Rik



reply via email to

[Prev in Thread] Current Thread [Next in Thread]