rakudo_2016.09-1_amd64.changes ACCEPTED into unstable

[Daniel Dehennin]

Daniel Dehennin <daniel.dehennin at baby-gnu.org> writes:


[...]

> We could switch moarvm to libffi:
>
> - it seems to solve at least the timeout issue on arm64
>
> - all failing tests are due to nativecall
>
> - it should fully support perl6 NativeCall

I prepared a feature/switch-to-libffi branch[1] for pkg-moarvm and test
the builds on amd64 and i386 using sbuild with schroots:

- rebuild of MoarVM feature/switch-to-libffi branch

- rebuild rakudo from unstable sources using my local MoarVM packages

The tests fails on both amd64 and i386

Test Summary Report
-------------------
t/04-nativecall/11-cpp.t               (Wstat: 65280 Tests: 1 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 21 tests but ran 1.
t/04-nativecall/13-cpp-mangling.t      (Wstat: 65280 Tests: 0 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 26 tests but ran 0.
Files=45, Tests=554, 47 wallclock secs ( 0.14 usr  0.07 sys + 41.54 cusr  3.22 csys = 44.97 CPU)
Result: FAIL

Regards.

Footnotes: 
[1]  https://anonscm.debian.org/cgit/pkg-rakudo/pkg-moarvm.git/log/?h=feature/switch-to-libffi

-- 
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6  2AAD CC1E 9E5B 7A6F E2DF
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 324 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-rakudo-devel/attachments/20161001/7d0c0c4a/attachment.sig>