Rakudo on arm (was: Re: New MoarVM, NQP and Rakudo packages (2016.07))

[Dominique Dumont]

On Tuesday, 13 September 2016 21:20:47 CEST Dominique Dumont wrote:
> How about a good old fashioned chroot like the one described there ?
>  https://wiki.debian.org/Arm64Qemu

I've setup an arm64 chroot on my laptop,

Good news: with libffi, the test don't hang.

Bad news: some tests fail: 

t/04-nativecall/10-cglobals.t ............ ok
t/04-nativecall/11-cpp.t ................. 
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 20/21 subtests 
t/04-nativecall/12-sizeof.t .............. ok
t/04-nativecall/13-cpp-mangling.t ........ 
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 26/26 subtests 
t/04-nativecall/13-union.t ............... ok
t/04-nativecall/14-rw-attrs.t ............ ok


Worse news : the package is still built even if some tests are failed.

Even worse: other arch also show test failure even though the package is built:

* armhf: https://buildd.debian.org/status/fetch.php?pkg=rakudo&arch=armhf&ver=2016.07.1-1&stamp=1469454744
* armel: https://buildd.debian.org/status/fetch.php?pkg=rakudo&arch=armel&ver=2016.07.1-1&stamp=1469452063
* powerpc: https://buildd.debian.org/status/fetch.php?pkg=rakudo&arch=powerpc&ver=2016.07.1-1&stamp=1469450586
* ppc64el: https://buildd.debian.org/status/fetch.php?pkg=rakudo&arch=ppc64el&ver=2016.07.1-1&stamp=1469450194

According to the logs, only amd64 and i386 (including kfreebsd variants) build fine.

Daniel, do you know why the package is build even though tests are failed ?

Other thoughts ?

All the best

-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org